Microsoft KB Archive/120725

{|
 * width="100%"|

BUG: dbdataready and DBDEAD Return FALSE After spid is Killed

 * }

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 : kbprogramming

Issue type :

Technology : kbSQLServSearch kbAudDeveloper kbSQLServPTK420