Designing ODBC applications for performance optimization
- Last Updated: October 7, 2020
- 1 minute read
- DataDirect Connectors
- ODBC
- Aha! 8.0
- Amazon Redshift 8.0
- Apache Cassandra 8.0
- Apache Hive 8.0
- Apache Spark SQL 8.0
- Autonomous Rest Connector 8.0
- Cloudera Impala 7.1
- dBase 7.1
- + 24
Developing performance-oriented ODBC applications is not easy. Microsoft’s
ODBC Programmer’s Reference does not provide information about
system performance. In addition, ODBC drivers and the ODBC driver manager do not return
warnings when applications run inefficiently. This chapter contains some general guidelines
that have been compiled by examining the ODBC implementations of numerous shipping ODBC
applications. These guidelines include:
- Use catalog functions appropriately
- Retrieve only required data
- Select functions that optimize performance
- Manage connections and updates
Following these general rules will help you solve some common ODBC performance problems, such as those listed in the following table.
| Problem | Solution | See guidelines in... |
|---|---|---|
| Network communication is slow. | Reduce network traffic. | "Using Catalog Functions" |
| The process of evaluating complex SQL queries on the database server is slow and can reduce concurrency. | Simplify queries. | "Using Catalog Functions" "Selecting ODBC Functions" |
| Excessive calls from the application to the driver slow performance. | Optimize application-to-driver interaction. | "Retrieving Data" "Selecting ODBC Functions" |
| Disk I/O is slow. | Limit disk input/output. | "Managing Connections and Updates" |