Comments
1 comment
-
Hi Phil,
What we give you here is straight out the error log. I'm afraid we've not looked into doing anything with that information.
However this information does give you the SPIDs of the processes involved (in this case 212 and 202). SQL Response may have captured the SQL process information, but as this is done by polling every so often it sadly may not have the exact processes. If you look on the performance tab you may be able to find those ids which will give you a little more information.
It also gives you the input buffer - which can contain the SQL that was executing. In this case however it refers to an RPC event (possibly calling a stored procedure).
I'll take a look tomorrow and see what else I can find out for you.
Add comment
Please sign in to leave a comment.
-Phil
Deadlock encountered .... Printing deadlock information
Wait-for graph
Node:1
KEY: 37:72057594042974208 (a1007ef552f7) CleanCnt:3 Mode:X Flags: 0x0
Grant List 3:
Owner:0x5ACAE540 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:212 ECID:0 XactLockInfo: 0x26012FF4
SPID: 212 ECID: 0 Statement Type: DELETE Line #: 188
Input Buf: RPC Event: Proc [Database Id = 37 Object Id = 2099048]
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x236D0EC0 Mode: U SPID:202 BatchID:0 ECID:0 TaskProxy:(0x248EE378) Value:0x1ccbc800 Cost:(0/1640)
Node:2
KEY: 37:72057594042908672 (c10061f3b367) CleanCnt:2 Mode:X Flags: 0x0
Grant List 1:
Owner:0x728C1B00 Mode: X Flg:0x0 Ref:0 Life:02000000 SPID:202 ECID:0 XactLockInfo: 0x236D0EE4
SPID: 202 ECID: 0 Statement Type: DELETE Line #: 138
Input Buf: RPC Event: Proc [Database Id = 37 Object Id = 98099390]
Requested By:
ResType:LockOwner Stype:'OR'Xdes:0x26012FD0 Mode: U SPID:212 BatchID:0 ECID:0 TaskProxy:(0x265CA378) Value:0x38f587a0 Cost:(0/3680)
Victim Resource Owner:
ResType:LockOwner Stype:'OR'Xdes:0x236D0EC0 Mode: U SPID:202 BatchID:0 ECID:0 TaskProxy:(0x248EE378) Value:0x1ccbc800 Cost:(0/1640)