November 11, 2009 at 6:10 am
Hi
I am seeing the dead lock issue .
After analyzing the deadlock graph , I could extract below information.
I could sense the dead lock is because of the one of the table TBL_TEST, this table just have primary key on the id column.
Could someone can explain how to crack this out.
The both the process is trying to 1 Update ,2 Delete and 2 insert operation.
None of the operation are related. The data row which both process are operation upon is completely diff.
process968b68
Waiting on -- KEY: 5:72057803847827456 (2c013b0aa399)
spid="57"
processc145c8
Waiting ON KEY: 5:72057803847827456 (2501b65fd56b)
spid = "56"
<keylock hobtid="72057803847827456" dbid="5" objectname="temp.dbo.TBL_TEST" indexname="TBL_TEST_P1" id="lock2456d2c0" mode="X" associatedObjectId="72057803847827456">
<owner-list>
<owner id="process968b68" mode="X"/>
</owner-list>
<waiter-list>
<waiter id="processc145c8" mode="U" requestType="wait"/>
</waiter-list>
</keylock>
<keylock hobtid="72057803847827456" dbid="5" objectname="temp.dbo.TBL_TEST" indexname="TBL_TEST_P1" id="lock2bdc26c0" mode="X" associatedObjectId="72057803847827456">
<owner-list>
<owner id="processc145c8" mode="X"/>
</owner-list>
<waiter-list>
<waiter id="process968b68" mode="U" requestType="wait"/>
</waiter-list>
</keylock>
November 11, 2009 at 6:25 am
Can you post the entire deadlock graph please?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply