Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Stuart
Starting Member
2 Posts |
 Posted - 2004-03-01 : 12:32:13
|
| On SQL Server 2000 I am running merge replication every minute, and don't want to write to the application log on a failure (there are multiple subscribers, and it uses huge amounts of space).Clearing the job's notification tab removes one event, but SQLServerAgent still raises one event id 203 e.g. "SubSystem Message - Job 'xxx' (xxx), step 2 - The process could not access database 'xxx' on server 'xxx'."Appending -HistoryVerboseLevel 1 -OutputVerboseLevel 0 to the Run job step does not help.Any ideas?Thanks,Stuart |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-03-01 : 12:53:49
|
| You can stop SQL Server from writing to the application log, but you can't control it just for replication. Here is how to do it for SQL Server:Start SQL Server with the -n option. Here is what BOL says about this option:Does not use the Windows application log to record SQL Server events. If you start an instance of SQL Server with -n, it is recommended that you use the -e startup option too; otherwise, SQL Server events are not logged.So use -n with -e. -e means write it to the Error Log. You want logging to occur so that you can troubleshoot problems.Tara |
 |
|
|
Stuart
Starting Member
2 Posts |
Posted - 2004-03-02 : 04:30:47
|
| Thanks, I will go with that. It does seem strange that turning off the job's notifications does not stop the notifications.Stuart |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-03-02 : 12:33:23
|
| Job notifications are different than messages being put in the Error Log or Event Log.Tara |
|
|
|
|
|
|
Stop merge entries in the application log