Traceflag 1222 for deadlocks
Use traceflag 1222 for deadlocks when monitoring SQL 2005+, and keep 1204 just for SQL 2000 instances. 1222 gives so much more information and doesn't cut off the SQL text.
![](https://secure.gravatar.com/avatar/56d260994d0c6b1f5632c8c5c5be0527?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
Hello,
We are pleased to annouce that this feature is now implemented as part of v4.0 release. Please check release notes for more details.
Thanks,
Priya
-
Brett Estes commented
Thank you, Mark. I use this blog as a reference point every time I evaluate deadlocks:
http://blogs.msdn.com/b/bartd/archive/2006/09/09/deadlock-troubleshooting_2c00_-part-1.aspxHis highlighted information is the information I always focus on.
-
DiGi commented
Well, SQL server 2008 and 2012 provides even better option for tracing deadlocks - Extended event "xml_deadlock_report". Output should be quite same but with less system overload that traceflag.
-
H Reyes commented
This will help a lot. The current one is truncating the SQL statements and the deadlock graph doesn't show up.
-
Unfortunately not at the moment Aaron. But we are reviewing it. I will update the forum as soon as we have made any progress on this.
Thanks,
Priya -
Aaron Foote commented
This would be very good to have.
Any ETA on when we can expect this feature? -
Don Ferguson commented
This is one that would really help. Can it be implemented in the next SQL Monitor 3 release?
-
Hi Gail,
We have this in our backlog so we're hopeful we can soon add this improvement to forthcoming releases...
Thanks for your votes
Adam