I've done quite a bit of research into web analytics lately, and I have found a couple of things. Google analytics Is a great tool, but it cannot be the only tool an organization relies on. Because it is a purely JavaScript based, it is unable to catch browsers that do not have JavaScript enabled, this includes the search engine robots, some hand held devices, as well as a percent of users that manually turn this off. That being said we need a tool to parse the log files from the server and to give us information about these users, as well as providing us with "on demand" stats where as Google's stats are next day. The server logs also contain a wealth of other information that we are collecting automatically, so we might as well take advantage of it.

I have come to the conclusion that we need to use Google Analytics but we also need a tool that reads the server logs. There are quite a variety of tools that would fill this need. Google recently purchased Urchin who's web analysis product runs Google analytics, costs about $3k and will work with the Google Mini, Urchin also gives the ability to read logs from server software other than IIS (like apache, the software used for open source applications) .

Urchin will be releasing another version shortly, and this will be the first release since the Google buyout. Another option is WebTrends Analytics it costs about $4k. It Like Urchin will read both IIS and Apache logs, and has a web interface for users. The last product is NetTracker, it runs about $4k for the software, and another grand for support. it was recently bought out by Unica. The administration of netTracker is not the smoothest, and the support seems to have declined on quality since the buy out.

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.

Whether you prefer developing in ASP, PHP or Colfusion, Adobe Dreamweaver and the WebAssist Super Suite extensions can turn an ordinary website into a dynamic database-driven workhorse that rivals those from professional developers costing tens of thousands of dollars.

Super Suite extensions for Dreamweaver

Just like a professional carpenter, the right set of tools can make all the difference in the finished product. In Dreamweaver, having the right set of extensions can not only allow you to build more extensive, usable websites, but they can also save you an immense amount of development time and frustration.

WebAssist Super Suite gives you The Power to Build Anything

The Super Suite extension package covers everything from website security, user administration, user login, site cookies, sessions, database administration, email processing, dynamic dropdowns, a full ecommerce shopping cart, a website import tool, Eric Meyer's CSS Sculptor, a full-featured text editor, dynamic Flash charts, dynamic Google map integration and a whole lot more!

Database-driven websites, e-commerce and more

The Super Suite set of extensions gives Dreamweaver users the tools to create every facet of a functional content management system, full featured forums with access-level rights, complete website database administration tools including search, add, edit, update and delete fuctions, full digital file upload and download features, and a complete ecommerce shopping cart system with fully customizable storefronts. All this is achieved through an extremely easy-to-use wizard interface which walks you through each step in simple, intuitive fashion.

Easy-to-use Dreamweaver wizard interface

Super Suite can be easily integrated into your current site Dreamweaver template. The wizards take you through the steps needed to configure your options, you choose your template, and Super Suite creates all necessary pages, navigation, recordsets, CSS and javascript. You simply upload the new pages and files to your server, and the new functionality is live, with the look and feel of your existing website.

Create advanced Dreamweaver websites without knowing any code

WebAssist Super Suite extensions are perfect for Dreamweaver users who are hesitant to dig into the code. The extensions create all the code for you, and you can easily return to the wizard at any time to make changes. Super Suite has some similar functions to Adobe Dreamweaver Developer Toolbox, but it includes one-of-a-kind extensions like the iRite WYSIWYG editor for integrating FCKeditor into your Dreamweaver websites, CSS Sculptor which allows you to create complete standards compliant websites in one easy operation, and Site Import which allows you to import complete websites including all HTML, CSS, script, Flash and image files onto your local drive.

Advice from a Super Suite user

As a Super Suite user, I have used all their extensions extensively in my client websites. The ease-of-use and the Dreamweaver integration make them a must-have extension bundle if you want to develop websites faster, create more intuitive and complex websites, and make more money as a website designer or developer.

Adobe Dreamweaver Compatibility

The WebAssist Super Suite package is an all-inclusive Dreamweaver toolkit which provides developers with all the necessary tools to make dynamic database-driven websites in Adobe Dreamweaver. The extensions are compatible with Dreamweaver 8 and Dreamweaver CS3 on both PC and Mac. PHP, ASP and ColdFusion are supported by all the extensions.