DOC: SQL Server Books Online KILL Topic Is Incomplete for SELECT Statement in the Remarks Section (312072)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
- Microsoft SQL Server 7.0
This article was previously published under Q312072
BUG #: 356068 (SHILOH_BUGS)
BUG #: 102113 (SQLBUG_70)
SUMMARY
The SQL Server Books Online documentation for the "'KILL' Transact SQL-Reference" topic is incomplete for the SELECT statement in the following "Remarks" 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.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 10/16/2003 |
---|
Keywords: | kbbug kbpending KB312072 |
---|
|