![]() ![]() Although it is almost impossible to write an ODBC application without catalog functions, you can improve system performance by minimizing their use. By caching information, applications can avoid multiple executions. Minimizing the Use of Catalog FunctionsĬompared to other ODBC functions, catalog functions are relatively slow. ![]() The guidelines in this section will help you to optimize system performance when selecting and using catalog functions. SQLGetTypeInfo is listed as a performance-expensive ODBC function because many drivers must query the server to obtain accurate information about which data types are supported (for example, to find dynamic types such as user-defined types). Retrieving Data and Selecting ODBC Functionsīecause catalog functions, such as those listed here, are slow compared to other ODBC functions, their frequent use can impair system performance: Optimize application-to-driver interaction Using Catalog Functions and Selecting ODBC FunctionsĮxcessive calls from the application to the driver slow performance Common ODBC System Performance Problems and SolutionsĮvaluation of complex SQL queries on the database server is slow and can reduce concurrency This white paper contains some general guidelines that have been compiled by examining the ODBC implementations of numerous shipping ODBC applications.įollowing these general rules will help you solve some common ODBC performance problems, such as those listed in the following table. In addition, ODBC drivers and the ODBC driver manager do not return warnings when applications run inefficiently. Microsoft's ODBC Programmer's Reference does not provide information about system performance. Developing performance-oriented ODBC applications is not easy. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |