Traces, traces, traces...
-
Since a few days I find messages in the eventviewer about traces:
19030 :
SQL Trace started.
Trace ID = '1'
Login Name = 'sa'
At the same time this trace is stopped:
19031 :
SQL Trace stopped.
Trace ID = '1'
Login Name = 'sa'
This is happening every minute now, clogging up at least the eventlog. What I am curious about is what proces is causing this. I've checked current activities & errorlog, but could not find there any indication on what is causing this. There are no jobs whcih can start a trace.
Every now and then a DBCC TRACEON/TRACEOFF command is issued, but I can explain those. I have stopped and started SQLServer, rebooted the server, but these messages keep appearing.
How can I find out what is causing this? And how do I stop this?
Greetz,
Hans Brouwer -
There could be server side traces created and run be the sp_trace_**** set of stored procedures. (I usually kick these sort of traces off from a scheduled job.)
You could run profiler to find the source. If it turns out to be from the server itself, search the sprocs/agent jobs for sp_trace
Steven
-
Tnx Steven, I followed your sugestion, but could not find anything with 'trace' in the output. Found out tho what caused it. I have a trialversion of Quest Spotlight running, stopped it and now the tracemessages have stopped. Further investigation of these messages showed they were generated by Spotlight. This is not to my liking.
Greetz,
Hans Brouwer -
Hans,
SQL Server 2000 logs trace information into event log from SQL 2000 PS2. Check KB307538 (http://support.microsoft.com/default.aspx?scid=kb;en-us;307538) maybe helpful.
To list all traces you have on the server, run
SELECT * FROM :: fn_trace_getinfo(default)
To delete a trace, assign a trace id and run:
sp_trace_setstatus @traceid=?, @status =2
-
I'm seeing similar behaviour here on our system, however the trace is started deliberately by us, but is stopped straight away by a random (non-admin) user. What's going on!?
-
What I've experienced with traces in 2005 is if you specify a stop time for the trace, the message in the log saying who started the trace is correct, but when the trace stops automatically, the message in the log gives the wrong user name.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverabilityWe walk in the dark places no others will enter
We stand on the bridge and no one may pass
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply