Millions of web designers and developers have chosen Adobe Dreamweaver as their software of choice for website creation. Even with the incredible amount of built-in functionality that comes standard with Dreamweaver, there are many web applications that require a vast amount of hand coding to implement. Web Developer Suite from WebAssist is a Dreamweaver extension bundle that helps eliminate hand coding and opens up a vast dynamic frontier for the average Dreamweaver user.

Web Developer Suite consists of the following individual WebAssist Dreamweaver extensions:

• DataAssist - for complete database administration
• SecurityAssist - for user management, login, cookies and sessions
• Digital File Pro - for mastering file upload and download
• Universal Email - for processing form email on your website
• Dynamic Dropdowns - for dynamic dropdown menu creation
• Cookies Toolkit - add server-side cookies with one click
• Pro Maps for Google - dynamic or static Google maps API integration
• Validation Toolkit - for validating any type of form information
• iRite - for integrating WYSIWYG text editors into websites
• Database Starter Kits - for both PHP and ASP

Each extension is installed individually within the Dreamweaver extension manager, and is accessed via the WebAssist toolbar added to Dreamweaver. The real value of the Web Developer Suite lies in the ability to code advanced website function in a fraction of the time it would take to hand code. Each extension operates from a wizard-like interface that clearly walks you through the steps needed to configure your task.

DataAssist creates complete database administration page sets with a few clicks of the mouse. Automatically generate web pages that add, delete, update, view or search your database. If you use Dreamweaver templates, DataAssist allows you to use your site template when generating pages. The resulting pages flow seamlessly into your website and are fully customizable via CSS.

SecurityAssist generates all the pages and code needed to create secure user registration and log in pages for your site. It teams up with Cookies Toolkit to utilize cookies and session variables to prevent unauthorized access to any pages you wish to restrict on your website.

If you need a Dreamweaver extension to control digital file upload and download, Digital File Pro is the extension of choice. Through a wizard-like interface, you can easily enable database file upload and download through your website. It's an excellent tool for webmasters who provide digital files such as MP3s, e-books, PDFs, images, photos, videos and any other type of downloadable file format.

Web Developer Suite also includes Universal Email, which is an extremely handy extension for emailing form input from your website. Universal Email even operates without a database, so it makes a great tool for emailing website contact form submissions. Emails can be formatted as text or HTML, and Universal Email includes a WYSIWYG HTML editor for creating your HTML email messages.

Pro Maps for Google inserts static or dynamic Google maps into your website. Addresses can be entered manually, from a file or even from your database recordset. The Google map API is fully configurable, with custom pointers, map controls and size. It's an excellent extension for inserting maps into dynamic websites.

Web Developer Suite also includes Validation Toolkit, which is WebAssist's form validation extension. Validate your form input client-side or server-side with a wide assortment of validation rules. By controlling form data input on your website, you can help reduce spam submissions and protect the integrity of your data.

The final Dreamweaver extension included in the Web Developer Suite is WebAssist's WYSIWYG form field text editor, iRite. Based on the popular FCKeditor, iRite allows you to insert a text editor in a Dreamweaver form for inputting valid XHTML code without needing any knowledge of HTML. iRite is a great extension for developing custom content management systems or just a simple way for clients to keep their own websites updated.

Web Developer Suite from WebAssist is an excellent addition to anyone's Dreamweaver toolbox. The cost of Web Developer Suite is a steal for the enormous amount of website function that is packaged in the bundle. Web designers can offer much greater website functionality to their clients and recoup the cost of the extensions in one project. There is no restriction on the number of sites you can build with Web Developer Suite, and no restrictive "per site" licensing. For web designers looking to push their websites to a new level, WebAssist Web Developer Suite is a must-have Dreamweaver add-on.

Your business can benefit from an online presence because of the flexible nature of online presentation.

It is possible to establish a cut off date for the sale of certain products and then use the same date to establish a new line. This can be accomplished through an automated dating system in web builder technology. You can even assign a certain product to show up in the clearance section of your site months ahead of time if you wish.

In a brick and mortar business environment there is a lot of work that has to be done whenever there is a change in sales promotions or when items need to be repriced and segregated for clearance sales. Staff members are required to stay late or come in early to make sure the new prices and displays are ready for the consumer.

In the world of online business you can create all the changes you want whenever it is most convenient. Because content information is tied to a dating system the web builder software will recognize those changes down to the minute.

If you've promised your customers a special sale beginning at a specific time it is possible to manage this change hands-free. When the time comes for the sale to begin the new information is assigned to the location you predetermined for it and customers gain immediate access to the sale prices.

Imagine the day after Thanksgiving, but without the hassle of actually having to show up for work on time. Many businesses enjoy the flexibility of making changes to their business site well in advance of the date the changes are to be put in place.

This idea may stand in stark contrast to the way you run your website. In many cases the only changes that can be made are alterations directed by the web designer. Often a web designer lacks the ability to make immediate and/or timely changes to your website. Businesses that use a web designer often need to make multiple requests for work to be completed on their site.

The growth of self-directed site design is due in large part to the need businesses have of being able to make immediate changes to their site if necessary. Due to the immediacy of the web it has also become important for businesses to learn to manage those changes quickly.

In a feat that might rival The North Pole and its inhabitants, webs builder technology seems to operate on a magical plane where things systematically change without the need for direct human intervention.

If you're a website owner have you ever had trouble managing even the simplest changes when you need changes made? It can be frustrating to know that the alterations of your website are contingent on the ability for someone else to view your needs as a priority. If your web designer doesn't view you as an immediate concern then you simply have to wait until they are good and ready to help.

Orchestrate your own business symphony by making sure every instrument comes in on time.

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.