Application Event log 19030/19031 Trace stop/start messages.

[David Hay]

We use Idera's SQL DM to monitor our production servers. I has a tool
to monitor long running queries and pulls data every six minutes. The
server in question uses SQL 2000 SP4, all the others are SP3A and do
not do this.
When I turn on Query Monitor, I am now getting 19030 and 19031 Trace
started/Trace stopped messages filling up the application event log.
Is there a way in SQL SP4 to turn these off? All my other monitored
servers are on SP3a and do not do this.

Thanks!

David Hay

[YKaeder]

I have the same issue with a Windows SP4 server and Idera DM. I did a search
on the Idera web site. Idera suggests the following action.

CAUSE:
By default, SQL server error logging records an event in the Windows
application log every time a trace is started or stopped.

RESOLUTION:
If you use the "-n" startup parameter, SQL Server error logging will not be
performed to the event log. Be aware that this will also prevent the logging
of other SQL server errors as events, including successful and failed
backups. If you need to see this information, you can still find it in the
SQL Server error log , located at "C:\Program Files\Microsoft SQL
Server\MSSQL\LOG" by default.

For more information, please see the Microsoft Books Online article on
Startup Parameters:
http://msdn2.microsoft.com/en-us/library/ms190737.aspx

Post by David Hay
We use Idera's SQL DM to monitor our production servers. I has a tool
to monitor long running queries and pulls data every six minutes. The
server in question uses SQL 2000 SP4, all the others are SP3A and do
not do this.
When I turn on Query Monitor, I am now getting 19030 and 19031 Trace
started/Trace stopped messages filling up the application event log.
Is there a way in SQL SP4 to turn these off? All my other monitored
servers are on SP3a and do not do this.
Thanks!
David Hay