FIX: Broken Connection Does Not Terminate Blocked SPID (122486)
The information in this article applies to:
- Microsoft SQL Server 4.2x
This article was previously published under Q122486
BUG# NT: 932 (4.2)
SYMPTOMS
An unexpectedly large number of client connections to SQL Server may be
observed using the sp_who command or performance monitor. Many of the
clients shown by sp_who have rebooted or otherwise terminated their client
applications. sp_who will show these clients to be blocked on one or more
other client processes.
CAUSE
If a client connection is blocked by a lock held by another process and the
client's connection to SQL server is abnormally broken (for example,
network problems, client GP fault, or client reboot), the spid used by that
client will not be freed until the blocking process releases its locks.
WORKAROUND
Clients should be sure to terminate their connection to SQL Server.
Applications should cancel long running queries and, if necessary,
explicitly close connections to SQL Server. This will tend to discourage
users from rebooting or terminating applications taking an extended period
of time to process SQL commands.
STATUS
Microsoft has confirmed this to be a problem in Microsoft SQL Server
version 4.2. This problem was corrected in the latest U.S. Service Pack for
SQL Server version 4.21a. For information on obtaining the Service Pack,
please contact your primary support provider.
| Modification Type: | Major | Last Reviewed: | 3/25/2000 |
|---|
| Keywords: | kbbug KB122486 |
|---|
|