The information in this article applies to:
SYMPTOMS
Under heavy deadlock conditions, certain locking patterns may cause
blocking locks to remain. This may appear as a spid exiting without lock
cleanup. For example a spid holding blocking locks may be KILLed or exit,
yet the locks it held may remain and continue to block others. Afterwards
sp_who may show the blocking spid as a newly-logged in process that holds
no locks in the database, yet is blocking others.
For more information on what constitutes normal or abnormal blocking, see the following article in the Microsoft Knowledge Base: Q162361 : Understanding and Resolving SQL Server Blocking Problems WORKAROUNDTo work around this problem, use standard techniques to reduce locking contention and deadlocks. This can include shortening the transaction path length, using lower transaction isolation levels, eliminating extraneous indexes, or ensuring that transactions acquire locks in the same order. STATUS
Microsoft has confirmed this to be a problem in SQL Server versions 6.0 and
6.5. This problem was corrected in the latest Microsoft SQL Server 6.5 U.S.
Service Pack. For information on obtaining the service pack, query on
the following word in the Microsoft Knowledge Base (without the spaces):
Keywords : kbusage SSrvGen SSrvLock kbbug6.50 kbfix6.50.sp4 kbbug6.00 |
Last Reviewed: April 15, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |