Post reply

Deadlock Trace

  • June 18, 2007 at 8:31 am

    #70195

    With a view to capture deadlocks information, i created following trace on my server:

    Events:

     

  • June 18, 2007 at 11:19 am

    #713610

    Could you list some details ..

  • June 18, 2007 at 1:19 pm

    #713633

    Oops i missed it.

    Events: Lockdeadlock & lockdeadlock chain

    Datacols: event class, start/end time,object id, object type,spid,host,text data

  • June 18, 2007 at 2:18 pm

    #713651

    Not to sound like a smart$%% or anything, but did you have a question about this or were you just posting what you did?

  • June 19, 2007 at 6:30 am

    #713797

    Ofcourse. I just missed it while copy-paste. As i said the question was i wanted to trace what transactions/sp cause deadlocks on my server. What could be the best possible way to do this. The trace i created above gives me listing of deadlocks on server but doesnot show which transactions/query cause it.

    Thanks in advance.

  • June 19, 2007 at 7:05 am

    #713818

    You'll need to turn on a couple of trace flags - DBCC TRACEON(3605, 1204)

    These will send the deadlock information to the SQL Server Error Log and will tell you the spids involved and the statements, sprocs, etc at the time of the deadlock.

    A couple of good articles to look at:

    http://www.code-magazine.com/Article.aspx?quickid=0309101

    http://support.microsoft.com/kb/832524

    MG

    "There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies."
    Tony Hoare

    "If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply