skip to main content
OpenEdge Data Management: DataServer for ODBC
Programming Considerations : Enhancing DataServer performance
 

Enhancing DataServer performance

When you develop a DataServer application, you can design it either to emphasize portability across data sources or to optimize the strengths of the DataServer's interaction with a particular aspect of the target ODBC data source. For example, you might write a query that gives you consistent results across databases or one that takes advantage of your data-source cursor management functionality.
In addition to influencing how DataServer applications perform through queries, you can control how the DataServer processes queries on a statement-by-statement basis. Some of the DataServer's default behavior might not be optimal for the application you are designing. The QUERY–TUNING phrase and startup and connection parameters give you the ability to control query processing.
Information on query tuning appears in the following locations:
*The remaining sections of this chapter, which document the QUERY–TUNING phrase.
*For information on tuning queries at compile time and runtime, see Query tuning with connection and startup parameters.
In this section: 
* Progress query types
* Query tuning
* Caching records
* Join by SQL DB
* Writing queries for performance
* Skip schema verification
* Replacing FIND FIRST for performance