FIX: Problems Using the KILL Command with a Stored Procedure (158792)
The information in this article applies to:
This article was previously published under Q158792
BUG #: 16064 (6.50)
SYMPTOMS
Using the KILL command to end a long-running stored procedure may cause the
computer running SQL Server to stop responding or go into a 100 percent CPU
spin. All existing connections cannot process, and any attempts to connect
will time-out. SQL Server cannot be shut down, and you must either kill it
or restart Windows NT. This problem should only occur if the stored
procedure is processing through a large cursor set.
WORKAROUND
Use the KILL command with discretion.
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server
version 6.50. This problem has been corrected in U.S. Service Pack 2 for
Microsoft SQL Server version 6.5. For more information, contact your
primary support provider.
SQL65SP2FIX
| Modification Type: | Major | Last Reviewed: | 10/3/2003 |
|---|
| Keywords: | kbBug kbfix kbusage KB158792 |
|---|
|