Microsoft KB Archive/312072

= DOC: SQL Server Books Online KILL Topic Is Incomplete for SELECT Statement in the Remarks Section =

Article ID: 312072

Article Last Modified on 10/16/2003

-

APPLIES TO


 * Microsoft SQL Server 2000 Standard Edition
 * Microsoft SQL Server 7.0 Standard Edition

-



This article was previously published under Q312072



BUG #: 356068 (SHILOH_BUGS)

BUG #: 102113 (SQLBUG_70)



SUMMARY
The SQL Server Books Online documentation for the &quot;'KILL' Transact SQL-Reference&quot; topic is incomplete for the SELECT statement in the following &quot;Remarks&quot; section:

KILL is commonly used to terminate a process that is blocking other important processes with locks, or to terminate a process that is executing a query that is using necessary system resources. System processes and processes running an extended stored procedure cannot be terminated.

Use KILL very carefully, especially when critical processes are running. You cannot kill your own process. Other processes not to kill are:

AWAITING COMMAND

CHECKPOINT SLEEP LAZY WRITER

LOCK MONITOR

SELECT

SIGNAL HANDLER

Do not issue a KILL statement against a SELECT statement if the SELECT statement is associated with the query that retrieved the list of server process IDs (SPIDs). If you issue a KILL statement against your own process, you will receive the following error message:

Server: Msg 6104, Level 16, State 1, Line 1 Cannot use KILL to kill your own process.

However, you can use the KILL statement to close a SQL connection for a SELECT statement.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Additional query words: BOL

Keywords: kbbug kbpending KB312072

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.