Post reply

Tracing Deadlocks

  • April 6, 2005 at 10:47 am

    #165063

    I liked article ‘Tracing deadlocks’ from 04/05/05 very much and found it very helpful.

    I was able to trace deadlocks in development environment.

    Now, I would like to do the same on production. I have two concerns:

    • DBCC TRACEON (3604)
    • DBCC TRACEON (1204)

    1. Does setting those trace flags in production environment effect performance in any way? We have a very critical application and can not accept any risks during daytime. But deadlocks of course happen during that time.

    2. When and how do I turn those flags off?  Does the order matter?

    • DBCC TRACEOFF (3604)
    • DBCC TRACEOFF (1204)

     

    I would really appreciate response.

    Thanks,

    Jane

     

     

  • April 7, 2005 at 7:55 am

    #551144

    I usually add these to the startup parameters of the server ( click on server in EM, properties, startup parameters - I add 1205 too.  ( -T1204   -T1205  -T3605 )

    To remove them remove them - The method I use writes to the error log so i get around 80Mb a day error log, so yes there is some slight performance degredation - depends on your hardware platform of course - and how important the deadlock info is.

    You need a service stop and start to enable these trace flags

     

    [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