When I start SQL Server Profiler, it says trace is starting at the bottom,
and may return rows for a few seconds, but then it stops saying "Trace is
stopped".

Event viewer does not show any errors, but does provide the following events
every few seconds.

SQL Trace ID 2 was started by login "xxxxxx\xxxxxx".
SQL Trace stopped. Trace ID = '2'. Login Name = 'xxxxxx\xxxxxx'.
SQL Trace ID 3 was started by login "xxxxxx\xxxxxx".
SQL Trace stopped. Trace ID = '3'. Login Name = 'xxxxxx\xxxxxx'.

It alternates between ID 2 and 3 several times per minute.

Does anyone have any ideas / suggestions?

Larry (Larry (AT) discussions (DOT) microsoft.com) writes:
Have you by chance enabled "Trace Stop time" on the first page in the
configuration?



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Erland,

No. This is not the problem. Any more ideas?

Thanks,
Larry

"Erland Sommarskog" wrote:

Larry (Larry (AT) discussions (DOT) microsoft.com) writes:
Seems like you need to set up a server-side trace to see which spids that
runs sp_trace_setstatus.

You can set up such a trace in Profiler, then select Export as SQL
Script. Then run the script, and the play with Profiler. You can use
fn_trace_gettable to get the data for the trace.



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx