December 17, 2008 at 5:01 am
Hi,
Please help me in understanding this deadlock graph
Please check the attachement for the graph
December 17, 2008 at 6:13 am
Most of it is not displaying. You should try zipping it up and posting it as an attachment.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 17, 2008 at 6:14 am
Or edit the post... that works too.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 17, 2008 at 6:18 am
Are these queries part of a bigger set of commands? Nothing there indicates why you'd receive a deadlock. You need to look at the statements prior to these two to see why the attempts to get exclusive locks is causing the deadlock.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
December 17, 2008 at 6:56 am
Hi Grant Fritchey,
I have edited the post and attached the deadlock graph
December 17, 2008 at 7:12 am
OK. Now that I'm seeing the full graph at last, I'll sound a little less foolish (but only a little). I'm seeing you running two updates, in different orders, the first is ihitting EDEPOSIT and then SECTIONS and the other is hitting EMPLOYEES and then SECTIONS. The cross point seems to be between EMPLOYEES and EDEPOSIT based on the two keylocks in the resource-list. Do you have a trigger between SECTIONS and EMPLOYEES?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply