Personal websites and business may not go hand-in-hand as far as you are concerned, but I urge you to think again. If you want to sell something, you may need to "sell yourself" first. People enjoy doing business with someone they know and like. More importantly, they want to know that they can trust you.

We are actually able to transact business all over the world due to today's technology. The problem with that can be a lack of personal service. However, with the internet, and especially with personal websites, we can feel as if we know someone that we have never actually met. We can know what a person looks like, we can know the sound of their voice, we can know all about their family, hobbies, dreams, future goals, etc.

When someone is surfing the web looking for a way to work from home, they are also looking for someone to partner with. Someone to mentor them and show them the way. They want to feel comfortable with a prospective future business partner.

If you want them to consider joining your opportunity, you have to be visible on the internet. You have to be willing to get personal and reveal yourself to them. Your site should be warm and inviting. It should provide information about you and your business opportunity. Give them a way to contact you.

This really is the way to gain business partners from all over the world, or from just the good old U.S. if your company is not international. Think about what you were looking for when you were searching for a home business. I don't know about you, but I felt a connection with my sponsor. I felt as if I knew her just by looking at her website.

That is what you want to create. You want to seem warm, friendly, and approachable. You want your reader to feel as if they already know you. A lady contacted me via email recently who was interested in my candle business. She practically told me her life story in that email, and it is probably because she felt like she knew me. She had seen my site and already knew all about me.

That is a good thing. It means that she felt as if I was someone she could talk to candidly. She must have thought that I would be approachable and would be receptive to her. Not everybody who contacts you will be so open. They may be wary of you and your business, but they contacted you because they found something of interest. This is when you provide them with honest answers to all their questions. It is also where you give them that personal attention that they are seeking.

Their state of mind when they contact you is not important. The fact that they made a connection is what matters. The reason for the connection was that they found your personal website and liked something they saw there. They were able to contact you because you provided them with either a phone number, email address, or both.

Do you see how this works? Prospects come to you. You do not have to "beat the streets" or chase your friends and family in order to build your business. This is not yesterday's network marketing, it is the new way. Believe me, it is also the best way. Many of yesterday's methods gave us a bad rap because they were so annoying.

Personal websites and business work well together. Get your own site up soon. It doesn't have to be fancy; just informative. Keep it simple and see what happens. I am sure that you will be pleased with the results. Remember to advertise your website and tell your friends about it. You cannot just build it and hope they will come.

One of the great debilitators in online business is simply the perceived (or real) lack of time. Business owners are used to moving forward. An online web presence can make them feel tied to an office chair learning skills they aren't sure they want to know.

It's not uncommon for those who deal in full time web design to have individuals contact them for a site design, but have absolutely no idea what they want. Furthermore when the designer questions them the response might be, "I don't know, just make it look nice."

Let's not forget the core values or mission of the business. Many business owners have no idea how to answer those kinds of questions. They may stare blankly for a moment or two and there's no more time for further deep thought so they go back to action - without answers.

In many cases it is possible to answer some of the questions needed, but it may require taking time away from a familiar setting. It may also require more time than you think you want to give.

If you can get to a place of concentrated contemplation you are likely to find yourself stripping ideas to their core to find out what your business is trying to accomplish and what your ultimate goals might be.

As with almost any project you can turn frustration around if you will just take the time to come to terms with your vision.

Sometimes we spend so much time 'doing' we never stop to ask the question, "Why?"

This process can be a bit like taking a bus that drives around the park. You keep looking at the flowers and the park bench and long to sit in the quiet shade of a tree and just absorb the calming atmosphere. You know they will have a positive effect on you, but for some reason you just can't seem to find the energy to get off the bus.

It seems to me there are some sites that are misguided or rarely guided that could benefit from the process of self-evaluation. These sites may look nice, but there is a sense of disconnection that may not be easy to identify, but it's fairly obvious to visitors.

Creative energy is at a minimum while business owners simply tackle what seem to be the most urgent details.

As more people gravitate to online business there needs to be a shift in the thinking of how one goes about doing business online. In many ways it can't be approached in the same way a traditional business is developed, yet that is typically the way many new web commerce ventures choose to tackle the subject.

You may discover your business will be more successful if you take some time for rigorous reflection. The time set aside can be a bit like an architect that takes the time to develop plans for a new building. You wouldn't expect the architect to simply tell a construction crew to, "Go out there and build - something."

Work at 'building' your online business in a comprehensive way. Your effort can develop a firm foundation for long-term success.

Don't be fooled by seeming simplicity. A lot of developers get comfortable with a certain way of designing a database for their web applications that they miss out on techniques they should rather employ to make things run faster and more efficiently. A lot of developers don't bear in mnd that the small site they are creating now might grow into something incredibly large and complex, and the database they designed has become bloated and doesn't scale well to meet the demands of the increased traffic.

This article hopes to provide web developers with a few techniques to help make their database and queries faster and more efficient.

1. Avoid Character Types

When you are designing a database, it is so easy to set all data types to the VARCHAR type as it can then contain any data you want; numbers or text. But character data is amongst the most inefficient data type you can get. If a field is only going to contain numbers, then make it one of the appropriate types (INT, DOUBLE, etc).

Also, wherever possible in your web development code, try to use numeric data types as opposed to characters. One of the most common things a script has to store are flags like whether someone answered yes or no to a question, etc. You could of course store it as 'Y' or 'N' but why not store it as 0 and 1?

The reason this makes a difference is when you have a database, for example, with over 500 000 entries, and are running a SELECT on that field, comparisons are processed a lot faster for numeric data types than character types. Also, if you need to return data to the calling script, numeric data is less memory intensive than character data. In addition, your web development language (PHP, ASP, etc) would also be able to process and perform functions on numeric data better than character data.

I am not trying to convince you never to use character data types. Sometimes it is a necessity, but if you can find ways to reduce the amount of character data processed by your SQL database, the better your server will cope.

2. Normalization

Normalizing a database is really quite a complex process. It is a process that describes a way to design a database structure to avoid repetition of data in your database and can lead to significant performance benefits if employed correctly. However, the entire process of normalisation is a bit beyond the scope of this article as it can fill books on its own, but any developer designing a database should seriously consider becoming knowledgable about normalisation and employing it in their own designs.

For a good tutorial on this process: http://www.keithjbrown.co.uk/vworks/mysql/mysql_p7.php

3. DateTime vs Timestamp fields

This actually relates to 1. a bit. The big difference to bear in mind here is that a field of type DATETIME is actually stored as a series of characters. A field of type TIMESTAMP is actually stored as an integer. So therefore, a more efficient way of storing dates is using the timestamp method. The timestamp has its drawbacks however. For one, you cannot store a date early than 1 January, 1970. Also, timestamps in your script will need recalculating to get to the character format. Because of this recalculation, it may not be better to store as timestamp. It really is a case of testing which format works better for your needs.

4. Use LIMIT where possible

In your queries, if you are doing a SELECT to a database and you only expect a certain number of results, using the LIMIT statement can speed your query up incredibly.

For example, if you have a table of users and you need to run a query to search for one users record, you can use a query like:

SELECT user_name FROM users WHERE user_id = 453;

This query is perfectly valid and will return the right result. But you also know there will only be ONE result. The query above will search the database, find what you want, but then still continue searching after that. It would run a lot faster if you could tell the query that once it has found what you are looking for to stop searching. LIMIT can do this, as this query shows:

SELECT user_name FROM users WHERE user_id = 453 LIMIT 1;

Imagine this scenario. You have a table called logins, that records every login from a user. It currently contains over 2 000 000 records, and you want to find the first time a user logged in. Now bear in mind that because this table inserts data over time, it is already sorted for by date. You could do the following query:

SELECT MIN(login_date) FROM logins WHERE user_id = 4876;

This will return the record you want, but SQL will now have to get all dates for that user, sort them and then return the lowest value to you. Our table is already date sorted simply because of the way it records data for us. So using LIMIT can be more effective:

SELECT login_date FROM logins WHERE user_id = 4876 LIMIT 1;

Because it is sorted, the first one will always be a users first login.

5. Avoid using LIKE

If you have tried to employ 1. above, then hopefully you will be in a scenario where you do not need to use LIKE all that much. LIKE is one of the most inefficient ways of searching a table. LIKE performs a text comparison search in a field and with no wildcards is as efficient as a direct comparison; i.e. WHERE name = 'Jane' is equivalent to WHERE name LIKE 'Jane'. It is when you start introducing the wildcard characters like '%' that things get really hairy.

If you do have to use LIKE, then at least try and make efficient use of the wildcards. These are '_' (underscore) and '%'. Let me explain all this with a real world example.

In a project I was involved in, we had a SQL database storing logs generated automatically from a mail server. Unfortunately, the mail server pretty much just dumped a very long string of text data into a field that contained the data we wanted. A script had to be written to find all logs that referred to a login by a user into the POP server. The only way we could do this was to search every record for a string in the msg field that had the text "User logged in" in it. The first query developed was something like this:

SELECT msg FROM logs WHERE msg LIKE '%User logged in%';

This query took on average of about 35 minutes to process. Obviously not an ideal situation. The way the LIKE worked here was that it had to parse through every single portion of each and every record in the msg field looking for text that matched "User logged in" anywhere in the text. We were able to determine eventually that the text "User logged in" occured at the end of that text in the msg field and so we altered the query:

SELECT msg FROM logs WHERE msg LIKE '%User logged in';

The '%' at the end was removed as we do not want to worry about text after because there is none. The query now only compares text to our string in the msg field at the end of the field and no longer parses through the entire piece of text stored in msg. The query now ran in under 2 minutes. (This was actually still too long, but how we optimised from there is a little beyond the scope of this article.)

Hopefully with all these elements put into practice on your next web development project, you can have a database that runs quickly, efficiently, uses as little resources as possible and wont grind to a halt when the load suddenly increases.