Under Construction!
SQL Server ...
Initially for my application I used an SQL server to keep track of all the data, but later I decided to switch to an LDAP server to hold most of my details. The reason behind this it that the LDAP server is built for a write few read many situations. I used queries to the LDAP server to populate dynamic select boxes holding customer, contact and product information. In addition to speed, the information in the LDAP server can be used in other applications and searched by most browser clients.
Though I used the LDAP server, I still used the SQL server to hold the individual call events. I planned the SQL tables in Microsoft access and then I downloaded the Microsoft Upsizing Tools to import the tables from Access to the SQL server. This is a very helpful tool because you can test your structure, or even design your application using the Access file and then use the upsizing tools to scale your application for load when need be.
The upsizing tool can be found at the following URL:
http://www.microsoft.com/accessdev/prodinfo/aut97dat.htm
Other tricks to make the SQL server fast are to make stored procedures. Stored procedures are pre-compiled SQL statements, which are run often by your application. They are called with the EXECUTE command. More information about this can be found in your SQL server manual. Another speed trick is to index the fields, which are searched often. Again, information on this can be found in the server manual.
Another feature of Cold Fusion that should be used is the CFTRANSACTION tag. This tag is put around a group of SQL statements. If any of the SQL statements fail, then the tag will drop any changes made to any statements before it. It is very useful in maintaining the integrity of your data.
Get your own Free Homepage
