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 |
|
gdeconto
Posting Yak Master
107 Posts |
 Posted - 2003-12-02 : 17:51:25
|
| noticed today that one of the sql servers I connect to had a pretty large error log (around 90MB).I cycled the error log manually using sp_cycle_errorlog.But, I have the following questions:1. is there a way to configure sql to automatically cycle the error log when it reaches a certain size? or does this fall under the category of creating a job to do this one a week or so?2. is there any way to control what events get logged?3 when executed, xp_logevent generates two lines in the error log. is there any sproc/facility that i can use to generate only a single lin in the error log?any help appreciated |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-12-02 : 18:28:32
|
| 1.Yes you would need to create a job. You could just schedule it to run once a week that way you don't have to write to code to figure out the file size.2.No, but you can log more events than SQL Server by default logs. You can do this with RAISERROR.3.I would doubt it.Tara |
 |
|
|
|
|
|
questions: sp_cycle_errorlog and large error log