BUG: dbdataready and DBDEAD Return FALSE After spid is Killed

Last reviewed: April 30, 1997
Article ID: Q120725

The information in this article applies to:

  - Microsoft SQL Server Programmer's Toolkit, version 4.2

BUG# 10129 (4.2)

SYMPTOMS

If a client program is waiting for data from a query that is locked and the spid corresponding to the blocked process is killed, dbdataready and DBDEAD will continue to return FALSE indefinitely. This occurs with MS-DOS, OS/2 and WIN16 DB-Library, it does not occur with NTWDBLIB.

WORKAROUND

If a DB-Library client application is waiting for a lock to be released and the corresponding spid is killed, dbdataready and DBDEAD will continue to return FALSE.

Implement a timeout by limiting the number of times your client application will check for dbdataready and DBDEAD while waiting for results from SQL Server.

STATUS

Microsoft has confirmed this to be a problem in DB-Library version 4.20.00. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: dblib
Keywords : kbbug4.20 kbprg SSrvDB_Lib SSrvProg
Version : 4.2 | 4.2 | 4.2
Platform : MS-DOS OS/2 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: April 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.