Welcome to dbbsrv.com

Important Networking Follow-Ups: How to Get Those Job Leads Calling When you leave a networking event, you may be buzzing at the prospects offered by all of those new contacts you made, but soon, the cold reality sets in. How will you be able to convert those contacts you made over a glass of wine into valuable business opportunities for you? Successful networking is all in the follow-up. If you’re looking for a job, following up is all the more crucial. Without touching base after a networking event, you become just another face in the crowd of job hunting hopefuls. The first important rule for following-up with networking contacts is to lay the foundations for the follow-up during the initial meeting. At networking events, there can be a lot of empty promises thrown around. Use that first meeting to convey the message that you haven’t gotten caught up in “networking fever” but instead that you are very serious about exploring the job opportunity that you’re discussing with your new contact. Ask the contact when would be a good time to follow-up with them, and then reiterate the information back to them at the end of your conversation: “I look forward to speaking with you Friday at 2 p.m.” If they don’t give you a specific time, then suggest one to them. This rule holds true even if your contact is giving you a lead on a job not with them but with another contact of their own. Let them know you appreciate the information by saying, “Thanks. I will plan on calling Mary on Monday afternoon at 1 p.m.” Not only will this convey your seriousness about the opportunity presented to you, but it may also get you some handy inside information, as the contact may reply, “Oh, no, Mary will be out of town until Thursday – call her then.” The next important rule to networking follow-ups is to follow up with EVERY lead a contact gives you. If a contact suggests that you call someone whom you know won’t really be able to help you in your job search, call him or her anyway. Otherwise, when your contact finds out you aren’t taking their advice, they may just decide not to give you any more the future and any business person can tell you that you never know from whom the most valuable lead will come some day. Keep the lines of communication open by giving any and all suggestions a whirl. Last but not least, do the actual following-up. Follow up with your contact exactly when you said you would, and in the exact manner you said you would (phone, email, letter, etc). If for some reason you can’t make contact at the arranged time, keep trying. If you haven’t made arrangements for a follow-up with a contact, then the rule of thumb is to follow-up with them as soon as possible after meeting them. Try to at least send an email or letter the next day saying what a pleasure it was to meet and that you look forward to talking more in the future, and then say in that note when you plan to follow-up with your contact by phone. Then, of course, stick to that new follow-up obligation. Even if the promises made by a contact while networking don’t pan out for you on the job front, don’t cross them off of your contact list. Keep them in the loop about your job search and your career goals. While they may not have been able to make if happen for you this time, you never know what they might be able to do for you in the future. Your most promising business contact may be someone you already know.

Web Hosting - Databases, What Are They and Do You Need One? 'Database' is one of the most commonly used terms that one encounters in web site design. Yet, what they really are and whether they're essential is often not clear to novices. A database is a collection of organized data, stored in files that have a specific structure. It's that organization and structure that allows for easy and rapid storage and retrieval. The need for a database generally only arises when you have a certain amount of information and that information needs to have some structure. If you have a half-dozen names and addresses to store, a database is usually overkill. If you have a blob of data with no relationships between any of the items in that blob, maintaining a database is usually more trouble than it's worth. Maintain a database? Yes, like other complex systems a database, to be effective, needs to be designed properly at the outset then kept 'tuned' for good performance. The alternative is to gradually allow the database to become more and more disorganized. That leads to difficulty in use, poor speed of retrieval and more frequent failures. With MySQL, Access or MS SQL Server, the three most common choices of database product for web sites today, setting up a database is relatively simple. Even those with limited technical skill can get one up and running just by following some simple instructions. But some thought should be given to how you want the information organized, and to maintaining the system during its lifetime. Suppose you have a set of names, addresses, email addresses, products purchased, date purchased and amount. If you have only a few dozen records it matters very little how these pieces are arranged and related. A database usually isn't even warranted in this scenario. Once you have several thousand or more records, it matters a lot. Speed, the ease of expanding the set of attributes (like adding, say, product category), and other issues come into play. Even those with little technical expertise, but a willingness to exert logical thought and invest some time, can build a very robust database. Think about how you would organize a set of data (called 'tables'). Should Name, Address, and Product be in the same table? Or should the personal information be stored in one table and any product information (product, price, ...) in another? Some experimentation may be needed to get it right, but the choices have an impact on how easy the tables are to maintain. It also affects the speed with which programs can fetch old data and store the new. Having a database also introduces new maintenance issues for the server administrator, since backups usually need to be done differently. Recovering a failed database is usually more complicated than simply re-copying files from yesterday. Ask your hosting company what tools and skills they have for dealing with any database system you consider. It's true that introducing a database creates more complexity and the need for additional thought and administrative effort. At a certain level, professional expertise will be needed. But clearly the advantages outweigh the costs in many cases. Companies large and small eventually use databases to store and organize data. At some point, you may be fortunate enough to be one of them.

Web Hosting - The Internet and How It Works In one sense, detailing the statement in the title would require at least a book. In another sense, it can't be fully explained at all, since there's no central authority that designs or implements the highly distributed entity called The Internet. But the basics can certainly be outlined, simply and briefly. And it's in the interest of any novice web site owner to have some idea of how their tree fits into that gigantic forest, full of complex paths, that is called the Internet. The analogy to a forest is not far off. Every computer is a single plant, sometimes a little bush sometimes a mighty tree. A percentage, to be sure, are weeds we could do without. In networking terminology, the individual plants are called 'nodes' and each one has a domain name and IP address. Connecting those nodes are paths. The Internet, taken in total, is just the collection of all those plants and the pieces that allow for their interconnections - all the nodes and the paths between them. Servers and clients (desktop computers, laptops, PDAs, cell phones and more) make up the most visible parts of the Internet. They store information and programs that make the data accessible. But behind the scenes there are vitally important components - both hardware and software - that make the entire mesh possible and useful. Though there's no single central authority, database, or computer that creates the World Wide Web, it's nonetheless true that not all computers are equal. There is a hierarchy. That hierarchy starts with a tree with many branches: the domain system. Designators like .com, .net, .org, and so forth are familiar to everyone now. Those basic names are stored inside a relatively small number of specialized systems maintained by a few non-profit organizations. They form something called the TLD, the Top Level Domains. From there, company networks and others form what are called the Second Level Domains, such as Microsoft.com. That's further sub-divided into www.Microsoft.com which is, technically, a sub-domain but is sometimes mis-named 'a host' or a domain. A host is the name for one specific computer. That host name may or may not be, for example, 'www' and usually isn't. The domain is the name without the 'www' in front. Finally, at the bottom of the pyramid, are the individual hosts (usually servers) that provide actual information and the means to share it. Those hosts (along with other hardware and software that enable communication, such as routers) form a network. The set of all those networks taken together is the physical aspect of the Internet. There are less obvious aspects, too, that are essential. When you click on a URL (Uniform Resource Locator, such as http://www.microsoft.com) on a web page, your browser sends a request through the Internet to connect and get data. That request, and the data that is returned from the request, is divided up into packets (chunks of data wrapped in routing and control information). That's one of the reasons you will often see your web page getting painted on the screen one section at a time. When the packets take too long to get where they're supposed to go, that's a 'timeout'. Suppose you request a set of names that are stored in a database. Those names, let's suppose get stored in order. But the packets they get shoved into for delivery can arrive at your computer in any order. They're then reassembled and displayed. All those packets can be directed to the proper place because they're associated with a specified IP address, a numeric identifier that designates a host (a computer that 'hosts' data). But those numbers are hard to remember and work with, so names are layered on top, the so-called domain names we started out discussing. Imagine the postal system (the Internet). Each home (domain name) has an address (IP address). Those who live in them (programs) send and receive letters (packets). The letters contain news (database data, email messages, images) that's of interest to the residents. The Internet is very much the same.