
Tracing Deadlock Graphs: Extended Events or Server Side Trace
Deadlock graphs are incredibly helpful for figuring out why queries are getting automatically killed off by SQL Server.
Deadlock graphs are incredibly helpful for figuring out why queries are getting automatically killed off by SQL Server.
If you use SQL Server’s blocked process report or collect deadlock graphs, occasionally you’ll come across things that look like this:
waitresource=“PAGE: 6:3:70133 " waitresource=“KEY: 6:72057594041991168 (ce52f92a058c)”