When a query is executed against a database, many pieces of information are exchanged between the client and the server. Query statements, result sets, and schema information are moved between the client and the server during the lifetime of most applications. The performance of many programs can be increased by using techniques that decrease this intensive data flow. One of the most common of these techniques is caching.
Caching is a mechanism that allows a database client:
to store data that would normally be sent immediately to a database server, then send the collected data together.
to retrieve data from a database server once rather than multiple times, and supply it as needed to the application.
Caching data locally can dramatically decrease the amount of network traffic incurred by a program. Furthermore, caching often allows the database server to optimize its resource usage. Both techniques result in better performance.
In some classes of the DB Interface Module, caching is employed automatically to provide the best performance in areas where it can safely be used. The classes RWDBInserter, RWDBReader, and RWDBEnvironmentHandle all provide caching options. These options, which are discussed in the following sections, allow specific choices to be made about how information is cached inside the DB Interface Module.
Caching can significantly increase application performance, but please see your Access Module guide for restrictions specific to your vendor.
Copyright © Rogue Wave Software, Inc. All Rights Reserved.
The Rogue Wave name and logo, and SourcePro, are registered trademarks of Rogue Wave Software. All other trademarks are the property of their respective owners.
Provide feedback to Rogue Wave about its documentation.