I love the deadlock enhancements added in 10.2. However, there are two specific areas of improvement that I'd like to see addressed.
1) If the SQL involved in a deadlock is truncated, display the VARBINARY form of the sql_handle (which can be parsed from the sqlhandle element of the deadlock XML) in a comment in the SQL textbox so that I can then attempt to get the full SQL Statement by pasting it into a query like:
SELECT text FROM sys.dm_exec_sql_text(0x020000009d274110419d8d97555a418c7904f5a528a993640000000000000000000000000000000000000000);
This is a significant issue for instances accessed using SQL generated from LINQ, which can be very lengthy.
For bonus points, automatically run that query with the appropriate value in the background in the appropriate instance and replace the truncated version of the SQL text with the complete version if it is found, either at the time the SQL text is captured in the repository or when it is displayed.
2) Display the KEY or PAGE information that is involved in the lock (which can be parsed from the waitresource element of the deadlock XML), which I could then use to find the value of the key. I have a script for using that KEY information to get the row data, which I'd be glad to share it upon request. The PAGE information can be used in an (undocumented) DBCC PAGE call to get the data present in that page.
