Options
Trace started / stopped messages in log
mksql
Posts: 10
It appears that SQL Response starts and stops traces when SQL profiling is enabled, generating approximately 2 log entries per minute.
Is this a known behavior of SQL Response? Is there a SQL Server flag that will suppress these messages only (without affecting other logging)?
Is this a known behavior of SQL Response? Is there a SQL Server flag that will suppress these messages only (without affecting other logging)?
Comments
SQL Response turns on some trace flags so that certain events will appear in the error log. Then SQL Response reads the trace information from the error log. That's how the detection of many events happens in SQL Response.