If you seriously want to debug, you’ve gotta use something like WinDbg. It’s tough, but powerful.
It’s also… Where do you even start? The most common thing to do is set a Break Point.
Figuring out where you wanna set it can be challenging.
– Sometimes you can capture a thread and step through the code.
– Sometimes you can find the call stack you want by searching through symbols
The problem with these is that stepping through code that runs in milliseconds has taken me over an hour at times, and call stacks often have cryptic names.
This is where tools like PerfView can help.
Erik does an excellent job going through PerfView and introducing people to debugging SQL Server.