March 27, 2012 at 3:00 am
I am running SQL Server 2008 R2 x64 Enterprise.
I have just encountered a deadlock where the victim had a higher Deadlock Priority. I was under the impression that this should never happen.
Has anyone else come across this scenario? Is there anything that can be done to guarantee that the Deadlock priority is honoured?
Deadlock graph attached.
Thanks,
Chris
March 27, 2012 at 4:25 am
I just used deadlock priority for the first time in a SP that was causing me serious headaches.
Say it ain't so!
My thought question: Have you ever been told that your query runs too fast?
My advice:
INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.
Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
Since random numbers are too important to be left to chance, let's generate some![/url]
Learn to understand recursive CTEs by example.[/url]
[url url=http://www.sqlservercentral.com/articles/St
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply