INF: Improved KILL Statement for DBCC CHECKDB

Last reviewed: June 27, 1997
Article ID: Q167608

The information in this article applies to:

Microsoft SQL Server, version 6.5 Service Pack 3

SUMMARY

Starting with SQL Server version 6.5 Service Pack 3, the Transact-SQL KILL statement works more reliably for DBCC CHECKDB.

MORE INFORMATION

Previously, DBCC NEWALLOC reliably responded to the KILL statement, but CHECKDB did not. For a brief period after submitting the DBCC CHECKDB command, it did respond, but after a few minutes (the exact period of time varies), it stopped responding.

Starting with SQL Server 6.5 Service Pack 3, the KILL statement terminates a DBCC CHECKDB process more consistently. A certain (and unpredictable) amount of time may elapse between issuing the KILL statement and the termination of the process, but this interval is usually less than 60 seconds.

Keywords : kbusage SSrvGen SSrvTran_SQL
Version : 6.5
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: June 27, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.