November 3, 2010 at 5:02 am
Dear All,
Can someone please advise on the below.
i) which trace is better to interpret the deadlock information either -T1204
or -T1222?
ii) How to view the deadlock graph in the SQLProfiler.
Thanks in advance.
Regards,
Ravichandra.
November 3, 2010 at 5:47 am
1222 is better. 1204 is the older traceflag, less info and harder to read/interpret.
Profiler - select the deadlock graph event. i think you might need the binarydata column for it. Check Books Online, should be there.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 8, 2010 at 12:10 am
Thanks Gail.
can you advise me on the below requirement.
I can see daily more deadlock information in SQLSeverLog and I want to report it to my manager that these deadlock issues happening because of this particular query and it's taking these resources and taking this much duraion.
So, please help me out how to get this query which is causing for deadlocks?
Thanks and Regards,
Ravichandra.
November 8, 2010 at 12:45 am
Post the deadlock graph? Without seeing it, it's hard to explain it.
There are lots of resources available to help if you want to do it yourself. Google should turn up a few, there's also a chapter in the book SQL Server MVP Deep Dives just on reading the deadlock graph
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply