The SQL error log has this nasty habit of getting big when I am not looking. There are only two ways to keep is at a normal size. One is to stop and start your SQL instance (Reboot, Restart, Stop and Start) and the other is to run this handy little script:
This will end the current log and start a new one. Why does this matter? The SQL Error log holds information about your backups, failed logins, SQL errors, edition information and other fun stuff. The bigger it is, the longer it will take SQL to load it into memory so that you can read it. Usually when you need to read it, you are in trouble so the slower it is, the more stressed you will be.
What is a good size? I usually try to get it to roll over around 10 MB. I use a monitoring tool and when the large error log alert is triggered, I have it run sp_cycle_errorlog for me so mine always stay a healthy size. You don’t need fancy tools to do this though. If you know about how fast your logs grow, you can set up a SQL Agent job to run it on a schedule to keep your logs healthy.
How many logs should I keep? This is completely up to you, but since I keep my logs so small, I try to keep 15 of them. Why so many? I do it so I can go back and see issues further back if needed. You can adjust the amount you keep by right clicking on SQL Server Logs in SSMS and selecting “Configure”
Super cool, but what about the Agent error logs? There is a script for them as well!
USE msdb; GO EXEC sp_cycle_agent_errorlog;
See? Healthy and Happy Logs! Your Logs will be clapping with joy.