Deadlock event

Question

Post reply

Deadlock event

adb2303

SSCertifiable

Points: 7588
More actions
September 15, 2011 at 4:36 am

#390412

Hi,
I had a deadlock event on one of our production boxes this morning. I'm unfamiliar with this type of deadlock and don't know where to start. I know the database that it occurred on, but that's about it.
Trace flags 1204, 1222 are running:
Thanks in advance,
Andrew

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

adb2303 SSCertifiable Points: 7588 More actions · Answer 1

adb2303

SSCertifiable

Points: 7588

September 19, 2011 at 9:13 am

#1383353

any ideas anyone? thanks,

free_mascot One Orange Chip Points: 27164 More actions · Answer 2

Enable traceflag 3605 which will help you to capture the information in sql log. Refer following link for further detail:

http://support.microsoft.com/kb/832524

HTH

---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."

adb2303 SSCertifiable Points: 7588 More actions · Answer 3

Hi,

We're already getting the deadlock events written to the log. I've turned on verbose logging for deadlock events, which produced the attached file, but I am unfamiliar with this type of deadlock. I don't know how to interpret this one...

Thanks,

Andrew

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 4

free_mascot (9/20/2011)
Enable traceflag 3605 which will help you to capture the information in sql log.

All 3605 does is redirect certain output (like DBCC Page) to the error log. It's got no use with deadlocks. The deadlock-related traceflags are 1204, 1205 and 1222.

Andrew, having both deadlock flags on is resulting in a mix of 2 deadlock graphs that's hellishly hard to tease apart. Please turn 1204 off, just leave 1222 on and post a new deadlock graph when another deadlock occurs.

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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

adb2303 SSCertifiable Points: 7588 More actions · Answer 5

OK - thanks for the advice. This is the only time I've seen one like this - the typical deadlocks we see are much easier to interpret. If one like this happens again, I'll post the graph.