SQL Server error log: SQL Stress ID_spotlight user; stopped...starting trace (4335461)

SQL Server error log: SQL Stress ID_spotlight user; stopped...starting trace

Every  5-10 minutes  SQL Server 2005 loggs stopping and starting trace

SQL Trace ID N was started by login "SpotlightUser" SQL Trace stopped.

Trace ID = 'N'. Login Name = 'SpotlightUser'.

The user is not associated with a trusted SQL Server connection

Certain versions of SQL Server stop the trace every 10 minutes despite it being configured to run continuously. Spotlight restarts it but a message is logged in the SQL Server error log every time this occurs. Unfortunately this is unavoidable and SQL Server 2005 is an unsupported version so Microsoft is not going to patch it up anymore.

We can't control the trace started and stopped messages being logged because SQL Server is stopping Spotlight's trace. It seems to think nothing is reading the trace results but we have tested this and deadlocks do get read by Spotlight so there is a reader present. As a workaround one can disable Deadlock collection in Spotlight. Select Configure | Scheduling option. Select instance name from top drop down list. Scroll down to Deadlock list. Check 'Override default settings' checkbox and uncheck 'Collect data when Spotlight is not connected' checkbox and hit OK.