Why does DBCC TRACEON (1204, 1222) not work?

Question

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?

Kin Shah · Accepted Answer · 2016-08-18 13:57:19Z

4

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.

answered Aug 18, 2016 at 13:57

Kin Shah

62.4k6 gold badges122 silver badges241 bronze badges

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
Commented Aug 18, 2016 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
Commented Aug 18, 2016 at 15:24

Add a comment |

1 Answer 1