Use extended events for deadlock "tracing" instead of a trace flag
If the SQL Server version is high enough, using extended events to capture deadlock information would be preferred to using a trace flag.
Blaž Dakskobler
shared this idea
SQL Monitor now supports extended events.
We have had a further suggestion to enable this per-server rather than globally, which has been added as: https://sqlmonitor.uservoice.com/forums/91743-suggestions/suggestions/31754800-enable-extended-events-per-server
Regards,
SQL Monitor Development Team
-
Hi Cathy ... If you want to stop SQL Monitor from turning trace on then instead of connecting to SQL Server using account with sysadmin rights, you can set up an account and give it only the minimum permission required. In this scenario, SQL Monitor wont be able to start the trace. Here is a link to help where the permissions needed are listed:
Thanks,
Priya -
Cathy
commented
I have turned off all alerts for deadlocks and I want to disable the trace flag 1204. I have executed DBCC TRACEOFF (1204, -1). My problem is that the next time SQL Monitor connects to the server, it re-enables the trace flag. My reasoning for turning the trace flag off is that of my 5 SQL servers and 160 + databases being monitored, only three databases are getting deadlocking errors. All of them are commercial off the shelf databases and I cannot do anything to eliminate the deadlocking. The deadlocking alerts account for nearly 80 percent of all alerts. I want to turn off the trace flag so the deadlocking errors are not written to my SQL log.
