September 6, 2005 at 10:36 am
I need to trace some deadlocks we are having on Production SQL servers and I have been thinking of using DBCC TRACEON (3605, 1204,-1) to get the info written to the log file.
Could any one advise on how it would affect the server performance?
I need to find information to help our team taking a decision. I have read on http://www.sql-server-performance.com/deadlocks.asp the overhead for doing this is minimal.
Thanks,
Jose
September 7, 2005 at 11:55 am
I turned on the traces several times on a busy OLTP system to debug dead lock issue before. As you said the impact was minimal.
September 7, 2005 at 12:31 pm
Just be wary of errorlog file growth. You might also want to increase the configured number of errorlogs to keep as well (default is 6, I use 20). Also check out BOL for DBCC ERRORLOG --> this rolls over the errorlog to a new file (to help keep them managable in size).
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply