Paul,
There is a known issue with lock escalation in SP2. SQL server will not
always release the shared lock if it needs to escalate it.
http://support.microsoft.com/default.aspx?scid=kb;en-us;306908
Use the link above and then select the link half way down the page 'ALL
FIXES in SP3'; search that page for 'escalation' and you should find it.
We have also had ODBC timeout issues where the connection has timed out
during a transaction which can leave locks lying about.
Hope that helps
David Lee
Database Administrator
Carlson Marketing Group
-----Original Message-----
From: Schlieper Paul
[mailto:mssqldba-ezmlmshield-x53416424.[Email address protected]
Sent: Thursday, May 27, 2004 2:44 PM
To: LazyDBA.com Discussion
Subject: SQL Server not releasing locks
Hi all,
Using SQL2K SP2 on Win2K SP4.
Occasionally, we see a situation where SQL Server does not release locks
held by one connection, and which blocks other connections.
Using sp_who2, I can determine that the spid at the head of the blocking
chain is "Sleeping", Command is "Awaiting command". Speaking to the user
whose spid is at the head of the chain, they claim that everything looks
normal from their end.
We used to see quite a bit of this in the days of SQL 6.5, but very rare
since moving to SQL 2K.
Does anyone have any ideas what could be the cause, or how to go about
tracking it down?
P
---------------------------------------------------------------------
TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY Website :
http://www.LazyDBA.com To unsubscribe:
http://www.lazydba.com/unsubscribe.html
For additional commands, e-mail: mssqldba-[Email address protected]
This message and any attachment are intended for use only by the individual to whom they are specifically addressed above, and may contain privileged or
confidential information. Any unauthorized dissemination or copying of this message or any attachment, and any use or disclosure of any information contained in
them, is strictly prohibited and may be illegal. If you are not the intended recipient of this message, please notify the sender immediately and delete it from any
computer.
Any views expressed in this message are those of the individual sender, except where the sender specifically states them to be the views of the company
MS Sql Server LazyDBA home page