using DBCC traceon 1204

  • We are having deadlocks problem on production server which is happening twice a week. Is there any resource problem by running DBCC traceon 1204 command on production box to monitor and get the deadlock block.

  • I continue to run 1204, 1205 and 3605 trace flags on my prod cluster ( did have lots of deadlock issues ) and this was the absolute way to get the information I needed, and prove it. Other than large transaction logs, which I re-initialise nightly I don't see any problems. You are writing a load of stuff to the log so make sure the drive is fast and has space - lots of it. There is an impact but you have to balance the cost against the resolution of the problem.

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

Viewing 2 posts - 1 through 2 (of 2 total)

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