Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

In the question Need Help Troubleshooting Sql Server 2005 Deadlock Scenario there was a suggestion of using DBCC TRACEON (1204, -1) to trace deadlocks globally.

When reading about this command in BOL it states that it should only be used while users or applications are not concurrently running statements on the system. Does it mean that we must be in singleuser-mode when enabling this trace-flag? And in addition, why is it required and is it important to follow the advice? (Just seems a bit hard to follow in a production system that is always running.)

share|improve this question
up vote 4 down vote accepted

This applies more to other trace flags (eg 610 for minimal logging) that affect the optimiser and important behaviours/optimisations

You should be OK with the deadlock trace flags 1204, 1205 and 1222

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.