I have executed DBCC TRACEON (1204, 1222) on several servers.

Some of them simply do not turn the trace flags on. The command brings the same expected informational message for each but some simply do not react.

DBCC TRACESTATUS(1204, 1222) delivers 0, 0, 0 in this case for both flags.

Why do they ignore it?


Running just DBCC TRACEON (1204, 1222) is per session level.

You should run DBCC TRACEON (1204, -1) globally.

See BOL- DBCC TRACEON for more details.

  • Yes, Sir, this seems to be my mistake here. However I still wonder why it did not even display on session level that it has been turned on... – Magier Aug 18 '16 at 14:19
  • @Magier maybe there is some issue here. There was another similar Q on StackOverflow recently stackoverflow.com/q/38836287/73226 – Martin Smith Aug 18 '16 at 15:24

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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