May 26, 2009 at 3:51 am
Hi Guys,
I have recently noticed that on my error logs, I’m seeing a lot of deadlock looking errors, it seems to be filling up the SQL logs and its taking an age to read the logs. The information being stored on the logs aren’t quite useful, can someone tell me if this information is useful.
Target Resource Owner:
ResType:LockOwner Stype:'OR' Mode: S SPID:156 ECID:0 Ec:(0x9CCD1340) Value:0xb3f4b891
Node:1 ResType:LockOwner Stype:'OR' Mode: S SPID:126 ECID:0 Ec:(0x6CCD1110) Value:0xb3f6b940
End deadlock search 188781 ... a deadlock was not found.
I can see deadlock trace graph, but I am also getting loads of the one mentioned above as well, what do I need to do to disable the one above, but I want to be able to see deadlock trace graphs.
Thanks in advance.
May 26, 2009 at 3:57 am
Looks like you have traceflag 1205 on. It gives lots of info on deadlock searches, most of which is not overly useful. Switch that traceflag off, and, if you know you're having deadlock problems, just enable 1204. If you're seeing the deadlock graphs, 1204 is also on.
Check the startup parameters for SQL, see if that flag is set there.
To switch it off, run this:
DBCC TRACEOFF(1205)
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 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply