Viewing 6 posts - 1 through 6 (of 6 total)
This seems to be a sql profiler bug - if you paste the xml posted above into an .xdl file then view it, the diagram does not show the <objectlock>...
March 30, 2011 at 10:13 am
Ok, now I understand the deadlock. It isn't a single resource being deadlocked, but is a the familiar kind of deadlock that everyone is familiar with.
Looking at the 1204...
March 30, 2011 at 9:05 am
Yes, tuning the selects gets rid of the deadlock. Unfortunately the selects are from adhoc reporting so there is only so much tuning we can do in advance. The...
March 29, 2011 at 2:13 am
Hi, This is the deadlock xml from a different, deadlock - but one that is exactly the same scenario as the previous postings. Again, two selects, one insert.
<deadlock-list>
<deadlock victim="processa9ddd048">
...
March 28, 2011 at 10:19 am
There is only one cpu on the server, so parallelism isn't involved.
We do have a number of options when it comes to avoiding the deadlock - nolock hints, changing...
March 28, 2011 at 9:43 am
Hi,
Some more information below, including the schema. Yes, that is the whole of the output, spid 60 looks like it is missing details - but that is all the...
March 25, 2011 at 11:31 am
Viewing 6 posts - 1 through 6 (of 6 total)