Just what is a 301 Redirect?

There seems to be a lot of confusion as to what to do when you move, delete, or want to redirect incoming web traffic from an 'old' web page to a 'new' web page. A 301 redirect is the most efficient method for web page redirection from an old web page to a new web page location. There is also some confusion as to how to handle the complete move or redirection from one web domain to another web domain. According to Google, "If you need to change the URL of a page as it is shown in search engine results, we recommended that you use a server-side 301 redirect instead."

How to Set Up a 301 Redirect

Depending on your web environment, there are several methods to set up a 301 redirect. A 301 redirect is not that hard to implement and it should preserve your search engine rankings for that particular page or web domain.

.htaccess 301 Redirection

The .htaccess file needs to be placed in the root directory of your old website. In this example, we are redirecting incoming web traffic from an old domain to a new domain.

Options +FollowSymLinks

RewriteEngine on

RewriteRule (.*) http://www.newdomain.com/$1 [R=301,L]

The .htaccess file is the most common method used for 301 web site redirection.

PHP 301 Redirection

You would place this code in a file at the old location.

Header( "HTTP/1.1 301 Moved Permanently" );

Header( "Location: http://www.new_location.com" );?>

IIS 301 Redirection

• In Internet Services Manager, you need to right click on the file or folder you wish to redirect
• Select the radio button titled "a redirection to a URL".
• Enter the redirection web page
• Check "The exact URL entered above" and the "A permanent redirection for this resource"
• Click on 'Apply'

That is all there is to it.

There are other methods in addition to set up a 301 redirection which include coding for ASP, ASP.NET, Java, CGI, Cold Fusion and Ruby on Rails. The above are the most common that I've encountered. When set up correctly, a 301 redirect will preserve your search engine rankings when it is necessary to move files around or switch, or consolidate, domain names.

You can definitely generate more business with a quality website. This may be the first line of communication between you and potential guests. A user friendly, well designed website is one of the greatest assets imaginable today for any business, organization or community group.

The great advantage of website development for a company is that the website will be available 24 hours a day, 7 days a week and can be viewed from anywhere in the world. So anyone can collect suitable information from the website at any time.

In today's business environment and to beat the competition large companies definitely need to develop a website. Many business owners use the excuse that their business is "word-of-mouth" and they do not need a website. But a great way to reinforce the personal recommendations of other clients is through professional website development.

Website development helps your company to increase product knowledge, maintain communication between you and potential clients, sell your products or services, generate leads for the business, increase the popularity of your company and much more.

Website development could provide all the information about their business, their products and also have provisions to sell their products online. Customers could be kept informed of up and coming promotions and product developments.

In the world today, not having a website is like not being listed in the telephone book. A website provides added visibility and credibility among consumers. When searching for a web designing company you will want to make sure they are able to provide everything you need. If your website is e-commerce based, you will want to make sure your web design company offers more advanced features such as search engine optimization (SEO). If your business is still lacking a website it is not too late to get started. Building and marketing a website can be done at a very affordable rate. Invest in your business today.

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.