Most beginners get screwed up when it comes to website building. Often than not, this is what exactly holding them back to make money online. If you are one of them, let me tell you one thing for sure; building websites is not as difficult as what you might think. Well, I am not saying that it is just a piece of cake either, but learning to build websites worth the investment and effort.

This article is about that, learning to build websites the easy way; much easier than you might ever think before...

Easy Website Theme

Everyone knows something about anything, including you. This can be your passion, hobby or experience from the job. You will get nothing if you keep that knowledge for yourself and even if you share them in the offline world. However, internet can be totally different. You can get paid for your knowledge sharing through various monetization plans. It works for me and will work for you too.

But then you might ask, If building website is that easy, why most fails building a successful website?

The answer is simply because, they fail to recognize and act upon the significant difference between offline and online trade. In the Internet, people look for information through Search Engine (SE) and web pages that ranked in the first page will benefit the most. Therefore, it is critical for you to optimize your web pages for certain targeted keywords so that you can rank high in the SE Ranking Position (SERP).

Easy Web Building Tool

You can build your website with other free website building software. Wordpress and Blogger are probably the most popular free web building tool available in the Internet. However, both offer less flexibility and professional looks since they are geared towards personal blog or online diary than for business ventures. Nevertheless, you can use both to get some feel of how to build a great website.

In my opinion, you should consider buying advanced website builder if you are serious about making money online. These softwares offer additional features compared to free tools such as flexible web editing and built in SE Optimization (SEO) tools. The initial investment can be easily recovered by the earnings potential you will be getting. I prefer Site Build It as my web building tool.

Easy Traffic Generation

Traffic is the one that will determine your success. Although the more traffic is better, nothing can beat the targeted one ever. Therefore, keep your marketing campaign to the most reliable and targeted sources so that you can enjoy very high conversion rate (percentage of visitors that turn to customers). Article marketing is free and among the most effective Internet marketing campaign.

Since you are the master or the so called "guru" in your field, writing a good article should not a big deal at all. Keep on writing great contents to attract more traffic. Best of all, it works forever. Part from that, you can connect your website with others through some social networking. Networking builds relationship and trust, which then makes your monetization effort much easier.

As you know there is lots of information out there on this subject. These days we are blessed being that we have the world of information at our finger tips. This of course can be helpful but it can also be overwhelming.

If you want to generate a real income then you will need to treat your venture with a serious mind set. One that is detailed and specific. I visit a number of forums online and I notice a certain pattern.

Those who succeed seem to be far more detailed in how they succeeded. Those who fail seem to be only detailed in blaming the reasons why they failed. They do not provide specifics as to what they did.

The reason maybe because they would have to defend their actions. They would be exposed and vulnerable to criticism.

By the way this criticism would be constructive because the majority of folks out there would genuinely point out what you are doing wrong and how you can go about fixing it.

You see those who succeed are not afraid of this. They understand that they may have shortcomings and welcome constructive analysis in order to move themselves closer to their objective.

The point I want to make is this. In order to bring anything from the world of ideas into the world of reality you will need to be detailed in your execution.

I mean you could not go to a bank and ask the bank manager for venture capital if all you have is ideas with no basis in reality. You will have to be specific and provide actual actions you can take to achieve your goal.

The same should hold true before you buy into any business opportunity online or build any website. Before you invest anything you need to provide a detailed outline as to what you are prepared to do and how you are going to do it - based upon the reality of your given set of skills and circumstances.

Once you do this I promise you that you will build a real business that will generate a real income because your execution will be detailed and specific and grounded in reality.

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.