How long has the server taken to generate 22GB of ErrorLog?
If you're not a fan of stopping/restarting your SQL Server (or, more likely, not allowed to...), then you might want to consider setting up a scheduled task to call `sp_cycle_errorlog` regularly, say once a week. That way you get a bit more more control over when you can archive off the old error logs. There are even blog posts out there that show you how to apply a bit more intelligence, and only cycle the error logs if they are above a certain size.
You also might need to think about cycling the Agent's log too - the SP to run here is `sp_cycle_agent_errorlog`.
↧
