BUG: Timeout Setting Ignored with Keyset-Driven Server Cursor

Last reviewed: July 21, 1997
Article ID: Q161353

The information in this article applies to:

Microsoft SQL Server, version 6.0
Microsoft Open Database Connectivity, versions 2.5 and 3.0

BUG #: 15679 sql60

SYMPTOMS

The SQL_QUERY_TIMEOUT setting may be ignored when using Microsoft SQL Server 6.0 keyset-driven cursors. The ODBC application may wait forever for the SQL statement to complete, even if the ODBC application uses the SQLSetStmtOption/SQL_QUERY_TIMEOUT option to specify the timeout for a query. The ODBC application may get the timeout expired error only after the SQL statement execution is completed.

WORKAROUND

To work around this problem, use a DYNAMIC cursor.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0 and Open Database Connectivity versions 2.5 and 3.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: vc vb odbc
Keywords : kbbug6.50 kbinterop kbother kbprg SSrvProg
Version : 2.5 3.0 6.0
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: July 21, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.