Feedback

Feedback

Did this article resolve your question/issue?

   

Article

Poor performance by SQL Server ODBC WP Driver 7.1 with dynamic cursor and "order by" query against a table with primary key constraint

Printable View

Information

 
TitlePoor performance by SQL Server ODBC WP Driver 7.1 with dynamic cursor and "order by" query against a table with primary key constraint
URL Namepoor-performance-by-sql-server-odbc-wp-driver-with-dynamic-cursor-and-order-by-query-against-a-table-with-primary-key-constraint
Article Number000118527
EnvironmentProduct: Connect 64 for ODBC SQL Server wire protocol driver
Version: 07.16.0417
OS: Linux
Database: SQL Server
Application: All supported applications
Question/Problem Description

SQLFetchScroll() calls are progressively slower with "ORDER BY" query when the SQL Server table has a primary key defined. And with a table without primary key, SQLFetchScroll() are performing consistently and faster. A query without an "ORDER BY" is showing the same behavior (progressively slower ) regardless whether a primary key is defined on the table or not. 

Some examples of these behavior found from the trace logs are given below. Check the "Time elapsed" part:

SQLFetchScroll() is progressively slower when fetching result set against table WITH primary key for SELECT query with "ORDER BY"-
2019-06-12 07:52:33.988547 (Time elapsed in microseconds :    88884) ppid=20485:pid=21583:tid=140417771779     EXIT  SQLFetchScroll  with return code 0 (SQL_SUCCESS)
2019-06-12 07:52:34.105283 (Time elapsed in microseconds :   111976) ppid=20485:pid=21583:tid=140417771779     EXIT  SQLFetchScroll  with return code 0 (SQL_SUCCESS)
2019-06-12 07:52:34.244798 (Time elapsed in microseconds :   134710) ppid=20485:pid=21583:tid=140417771779     EXIT  SQLFetchScroll  with return code 0 (SQL_SUCCESS)
2019-06-12 07:52:34.407466 (Time elapsed in microseconds :   157723) ppid=20485:pid=21583:tid=140417771779     EXIT  SQLFetchScroll  with return code 0 (SQL_SUCCESS)

SQLFetchScroll() is consistent and fast  when fetching result set against table with NO primary key for SELECT query with "ORDER BY":
2019-06-12 08:02:20.199863 (Time elapsed in microseconds :    22981) ppid=22881:pid=23874:tid=140298961196     EXIT  SQLFetchScroll  with return code 0 (SQL_SUCCESS)
2019-06-12 08:02:20.227517 (Time elapsed in microseconds :    22743) ppid=22881:pid=23874:tid=140298961196     EXIT  SQLFetchScroll  with return code 0 (SQL_SUCCESS)
2019-06-12 08:02:20.254758 (Time elapsed in microseconds :    22432) ppid=22881:pid=23874:tid=140298961196     EXIT  SQLFetchScroll  with return code 0 (SQL_SUCCESS)
2019-06-12 08:02:20.281789 (Time elapsed in microseconds :    22186) ppid=22881:pid=23874:tid=140298961196     EXIT  SQLFetchScroll  with return code 0 (SQL_SUCCESS)

SQLFetchScroll() is progressively slower when fetching result set against table WITH primary key for SELECT query without  "ORDER BY":
2019-06-12 08:09:33.266405 (Time elapsed in microseconds :    89521) ppid=22881:pid=25116:tid=140616344667     EXIT  SQLFetchScroll  with return code 0 (SQL_SUCCESS)
2019-06-12 08:09:33.383557 (Time elapsed in microseconds :   112228) ppid=22881:pid=25116:tid=140616344667     EXIT  SQLFetchScroll  with return code 0 (SQL_SUCCESS)
2019-06-12 08:09:33.523991 (Time elapsed in microseconds :   135570) ppid=22881:pid=25116:tid=140616344667     EXIT  SQLFetchScroll  with return code 0 (SQL_SUCCESS)
2019-06-12 08:09:33.686338 (Time elapsed in microseconds :   157383) ppid=22881:pid=25116:tid=140616344667     EXIT  SQLFetchScroll  with return code 0 (SQL_SUCCESS)

SQLFetchScroll() is progressively slower when fetching result set against table with NO primary key for SELECT query without "ORDER BY":
2019-06-12 08:12:06.894300 (Time elapsed in microseconds :    89139) ppid=22881:pid=25538:tid=139859270121     EXIT  SQLFetchScroll  with return code 0 (SQL_SUCCESS)
2019-06-12 08:12:07.015621 (Time elapsed in microseconds :   116388) ppid=22881:pid=25538:tid=139859270121     EXIT  SQLFetchScroll  with return code 0 (SQL_SUCCESS)
2019-06-12 08:12:07.164752 (Time elapsed in microseconds :   144130) ppid=22881:pid=25538:tid=139859270121     EXIT  SQLFetchScroll  with return code 0 (SQL_SUCCESS)
2019-06-12 08:12:07.341358 (Time elapsed in microseconds :   171755) ppid=22881:pid=25538:tid=139859270121     EXIT  SQLFetchScroll  with return code 0 (SQL_SUCCESS)

Steps to Reproduce
Clarifying Information
Error MessageN/A
Defect NumberDefect XDBC-15344
Enhancement Number
Cause
Dynamic cursor enhancements for SQLServer Driver were added recently. It was not there in the driver version 07.16.0417
Resolution
Fixed in hot fix 07.16.438.

Refer to Connect and Connect64 for ODBC hot fix download and install instructions  for instructions on how to download and install the hot fix.
Workaround
Notes
Last Modified Date9/11/2019 5:28 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.


Copyright © 2022 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.

Progress, Telerik, Ipswitch, Chef, Kemp, Flowmon and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.

Terms of Use Privacy Center Security Center Trademarks License Agreements Code of Conduct Careers Offices
Do Not Sell My Personal Information