Database Tips: Limit Changes

A database is an excellent place to store data. As we store larger and larger volumes, we need to process our database in the most efficient way possible.

As more users connect we should aim to limit the number of database writes and updates. Most database transactions tend to be inquiries and reads of values (‘what is this customer balance?”, “How many of this product in stock?”, etc.).

Crystal Reports usually only read databases. We saw an application once where the account tables rolled over the period numbers of each transaction every month. This increases the risk of data damage if the process ever goes wrong and as volumes increase the process becomes a larger and larger processing burden.

Design your database and application to minimize any bulk processing and changes to transaction records. Change database values only if you have to.

This article is copyrighted by Crystalkeen, Mindconnection, and Chelsea Technologies Ltd. It may be freely copied and distributed as long as the original copyright is displayed and no modifications are made to this material. Extracts are permitted. The names Crystal Reports and Seagate Info are trademarks owned by Business Objects.