|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: Thursday, November 15, 2012 9:55 PM
Points: 226,
Visits: 114
|
|
First off, kudoz to Siva! I have a more clear picture now that I can better read through the log. I definitely have a bit of reworking to do, though I do not have the luxury of always accessing objects in the same order all the time. But that's a story for another time. I was hoping I could get a lamen's explanation for deadlocks that read:
"Transaction (Process ID ###) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim. Rerun the transaction.."
It then prints out node after node of what appears to be chinese. From MSDN I gathered that it's attempting to reroute the Query somehow. Is this worse than the regular deadlocks discussed in the article? And what the heck is it trying to do?
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, December 26, 2008 1:58 PM
Points: 1,
Visits: 2
|
|
Hello, Does somebody has idea how to identify rows that are involved in deadlock? I can trace deadlock information including SQL statements but I still can't see bonded values or any other information that helps to identify rows. Appreciate your attention! Thank you.
|
|
|
|
|
SSC Veteran
      
Group: General Forum Members
Last Login: 2 days ago @ 8:47 AM
Points: 279,
Visits: 1,024
|
|
Hi Shiva Nice post about TF information.. I would like to know Owner:0x0000000BA7ED6780 this shows in result of Trace flag output.. And how i can know which table are locked from TF 1204 output.
Aim to inspire rather than to teach. SQL Server DBA
|
|
|
|