April 11, 2015 at 4:29 am
There's not enough here. These are part of a greater process. That other process has other statements. You need to determine the order in which these statements are occurring. This looks like a classic deadlock caused by two different processes accessing objects in differing orders. Probably part of the process reads from the same table that it's inserting into. Figure that out and you can determine how to go about fixing the deadlock.
Also, remember that deadlocks are fundamentally performance issues. If everything runs very fast, you'll never see a deadlock. From the look we have at this query, it might need to be tuned. Actually, from the look at the query, with all the VARCHAR(8000) over and over, I'm concerned that maybe your database needs to be redesigned a little bit.
"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 post 1 (of 2 total)
You must be logged in to reply to this topic. Login to reply