DeadlockResolveNames Process

Nov 3, 2016 at 6:06 PM
This is great stuff. I have run into one issue on a 2008 R2 instance. There are three processes within the deadlock graph. The second one has a transactionname of DeadlockResolveNames with a spid < 50. This causes much of the information to be incorrect or missing because the actual other process ends up being #3. So far, the only workaround I've thought of is a Case statement to check for the spid being <= 50 for process 2. Thanks.