Contents Index Always use a transaction log Normalize your table structure

ASA SQL User's Guide
  Monitoring and Improving Performance
    Top performance tips

Increase the cache size


Adaptive Server Anywhere stores recently used pages in a cache. Should a request need to access the page more than once, or should another connection require the same page, it may find it already in memory and hence avoid having to read information from disk. This is especially an issue for encrypted databases, which require a larger cache than unencrypted.

If your cache is too small, Adaptive Server Anywhere cannot keep pages in memory long enough to reap these benefits.

On UNIX, Windows NT/2000/XP, and Windows 95/98/Me, the database server dynamically changes cache size as needed. However, the cache is still limited by the amount of memory that is physically available, and by the amount used by other applications.

On Windows CE and Novell NetWare, the size of the cache is set on the command line when you launch the database server. Be sure to allocate as much memory to the database cache as possible, given the requirements of the other applications and processes that run concurrently. In particular, databases using Java objects benefit greatly from larger cache sizes. If you use Java in your database, consider a cache of at least 8 Mb.

Tip 
Increasing the cache size can often improve performance dramatically, since retrieving information from memory is many times faster than reading it from disk. You may find it worthwhile to purchase more RAM to allow a larger cache.

For more information, see Using the cache to improve performance.


Contents Index Always use a transaction log Normalize your table structure