Using SQL Compliance Manager 5.6 with SQL Server 2016 and older servers, the SQL Server error log gets flooded by messages such as:
SQL Trace ID 3 was started by login "CORPSOME_LOGIN".
SQL Trace stopped. Trace ID = '3'. Login Name = 'CORPSOME_LOGIN'.
The login referenced is the service account we are using for SQL Diagnostics Manager, and is included in the Trusted Logins on the server config.
We have the collection method set to Extended Events, but apparently that method doesn't apply to some things, or there is a bug.
- Is this a bug?
- If it's not a bug, is there any way that I can configure SQL Server or SQL Compliance Manager to eliminate these log messages?