Normally, if you want a professionally designed, custom-built website for your new virtual assistant business, you should be prepared to spend at least a few hundred dollars.

But, all that can change if you know where to find the best deals and the best designs for the lowest price.

First, it costs more to have a brick-and-mortar company design a website for you. Have you seen those newspaper ads that offer a 5-page website for $500? These are probably companies with physical locations. They have to charge more simply to pay for their overhead: office rent, designers' wages, advertising costs and so on.

Therefore, it would be wise to use a virtual assistant (VA) instead! As you already know, VAs often work from home so they do not have high operating costs like a big company does. On the other hand, a VA will be able to design images with quality similar to (or better than!) those of designers from big companies.

However, choose your VA with care. The best way to find the right VA for your project would be to go to visit the website of a VA association. There you can post your RFP (request for proposal) and have hundreds of talented VAs bid on your project, so you will get the best deal. You will also be able to choose your designer based on her experience, past transactions and client testimonials, so your value for money is secured.

Another route you can take is to purchase the Virtual Business Startup System, created by Tawnya Sutherland. It comes with several beautiful, easy to use templates, perfectly suited for a new VA. The templates are easy to edit wth the help of WYSIWYG (what you see is what you get) programs such as Microsoft Frontpage, Macromedia Dreamweaver and so on.

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.

There are a number of different browsers that you must compensate for when designing your webpage's in any format (CSS, tables etc.), some of the most common browsers are : Internet Explorer 6/ 7, Firefox and Safari. The main issues that arise with CSS design is that all browsers interpret CSS differently, for example Firefox does not understand some of the CSS commands that Internet Explorer does and vice a versa.

One of the main issues I have found when designing with CSS is a problem with margins in Internet Explorer 6. I found that when using a float on a div tag that also had a margin set, the margin would actually double and then knock the whole pages layout out. After numerous late nights and an insane amount of coffee I finally found a solution to this double margin bug. By inserting a simple line of code the double margin no longer double ! That solution is as follows, by adding this line of code to your CSS div tag 'display: inline'.

Another problem I have found with CSS in Internet Explorer 6 is a problem when trying to define a div tag that has a smaller size than the base font size. This problem again can be fixed with a simple line of code this time all we need to add is the following line of code to the div tag: 'font-size:0px'. There is also another solution to this problem that should have the same effect, because the div tag auto stretches to compensate for content overflow adding 'overflow: hidden' should also resolve the problem.

Unfortunately I have been unable to cover all of the cross browser issues that you may experience when designing with CSS, but most of the problems that you may encounter can be resolved pretty easily with simple trial and error. Happy designing!