Perhaps an unclosed transaction? I've had that happen, even with
shrink-wrapped software.

-----Original Message-----
From: Schlieper Paul
[mailto:mssqldba-ezmlmshield-x53416424.[Email address protected]
Sent: Thursday, May 27, 2004 8:44 AM
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]




MS Sql Server LazyDBA home page