March 1, 2005 at 7:45 am
You can periodically cycle the logs without rebooting. sp_cycle_errorlog or something like that will work. I had a server that never went down and we had the same issue, so we cycled them every week.
March 1, 2005 at 10:04 am
To cut directly to the chase:
use master
go
dbcc errorlog
go
checkpoint
go
It works well as a scheduled task.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
March 2, 2005 at 1:28 am
Thanks rudy
Brilliant - I'll shall apply a scheduled task to all our SQL Servers on a period base
![]()
March 2, 2005 at 2:34 am
We've got something along the lines of what Steve is suggesting. However, the stored proc that does this renames the log file so it doesn't get automatically removed.
--------------------
Colt 45 - the original point and click interface ![]()
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply