Posted by monkeybrains on 10/07/05 21:24

Just wanted to add a usage note here. I was pestered by the same
situation (event log overload from transaction replication on 40+ DBs).

I was able to suppress the backup / restore events in the Application
Event Log, resulting from SQL Log Shipping with these steps:

1) Go to the SQL Server Properties via Enterprise Manager (i.e. right
click the server and go to properties)
2) General Tab
3) Startup Parameters
4) Add new startup parameter--> /T3226
5) Apply / close dialog
6) Restart SQL Server instance

I am still able to view my backup / copy / restore history from the Log
Shipping Monitor or from the histories of each individual SQL Agent
job. That is much cleaner for my purposes.

Good luck -
Dave


Erland Sommarskog wrote:
> Mike (mjorlando@campsystems.com) writes:
> > Thanks Erland but I'm still not achieving my objective. Neither DBCC
> > TRACEOFF (3226) nor DBCC TRACEOFF (3001) stops the logging. I tried it
> > on the Master and the msdb databases and nothing changed. Should this
> > command be run against a different database? Mike
>
> Of course not. TRACEOFF turns off the trace flag! :-)
>
> I didn't specify how to should activate the flag, because I was not
> given any details on that. The simplest might be to add to the command
> line (you can do this from Enterprise Manager), but it requires a server
> restart).
>
> I believe that DBCC TRACEON from a query window affects that process only,
> nut adding -1 affects the server level. But I am very foggy on that point.
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
>
> Books Online for SQL Server SP3 at
> http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

[Back to original message]