SOS - How to interpret the profiler trace to find out the reason of deadlock?

  • zxmgh

    SSC Eights!

    Points: 911

    All,

    Thanks in advance for your help. Any help is appreciated.

    I have a urgent production deadlock issue. Because of the deadlock, one of the import applications is killed by SQL Server.

    I tried to find out the reason of deadlock. I run the SQL Profiler and I use the following eventclass:

    Lockeadlock

    Lockeadlock Chain

    Lock:Timeout

    Audit Login

    Audit Logout

    ExistingConnection

    RPC:Completed

    RPC:Starting

    SP:Completed

    SP:Starting

    Exec Prepared SQL

    Prepare SQL

    SQL:BatchCompleted

    SQL:BatchStarting

    SQL:StmtCompleted

    SQL:StmtStarting

    Unprepare SQL

    In the trace log file, I can only found a line under "Lockeadlock" eventclass, I can't find anything under "Lockeadlock Chain" eventclass.

    Here is the info from that line:

    EventClass:   Lockeadlock

    BinaryData:   0X00050700F4182A680000000000000000

    Integerdata:  24026

    Reads:         

    Writes: 

    StartTime:    2006-06-06 13:01:12.053

    EndTime:      2006-06-06 13:01:14.100   

    SPID:           140

    ClientProcessID: 9720  

    ApplicationName: e:\MyProgram.exe  

    TextData:        

    DatabaseID:   7 

    ObjectID:      1747589364 

    IndexID:       0 

    Mode:         Share 

    Duration:     2046  

    DBUserName:

    Hostname:    AppServer01  

    Please help!!!

     

     

     

  • zxmgh

    SSC Eights!

    Points: 911

    Another thing I want to mention is if I highlight that line, I saw the following two words:

    Table lock

Viewing 2 posts - 1 through 2 (of 2 total)

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