Posted by Erland Sommarskog on 06/08/05 18:17

debian mojo (debian_mojo@yahoo.com) writes:
> i'm encountering a strange a deadlock problem on my remote server
> which is used to give application demo to the client. It has happened
> that on one of the databases a deadlock situation is taking place.
>
> What is the most detailed way to detect such the cause of such a
> deadlock to the innermost level of detail, like what statements, stored
> procedures and locks are causing the deadlock to occur.

DBCC TRACEON (1204, 1)
DBCC TRACEON (3605, 1)

It's common to add these as start up parameters (best done from Enterprise
Manager).

This gives you a deadlock trace to the SQL Server log. Unfortunately,
though, it's a bit cryptic.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

• Next in forum: Re: Newbie question...
• Prev in forum: Re: Connection is busy with results for another hstmt & Win2003 SP1
• Thread view: Re: Deadlock detection problem! help

[Reply to this message]