What are the implications of enabling trace flag 1222 - write deadlock information to the log?

Question

DBCC TRACEON (1222) -- writes deadlocks to the errorlog

has anyone monitored if having this trace flag enabled would increase any WAIT_TYPE in particular or accrue any performance problem in any situation?

For this question, let's consider that there are not many deadlocks, only occasionally.

Answer 1

Based on many things I have heard around I currently have the following opinion:

There is very little overhead in enabling the trace flag unless you’re experiencing lots of deadlocks, which would cause a large amount of deadlock graphs to be written to the error log. However, it doesn’t sound like this is the case so it should be safe to enable the trace (it can always be turned off at any point with an instance restart).