October 11, 2014 at 7:26 am
Errorlog is growing very fast in my sqlserver2012 instance, due to this the disk getting full frequently.
everytime recycling and removing old errrorlog files.
is there any way to restrict the Errorlog not to grow fastly OR any suggestions please ?
Thanks in advance.
October 11, 2014 at 10:36 am
see what message is getting written to the errorlog to fill it and deal with whatever is causing it.
---------------------------------------------------------------------
October 11, 2014 at 12:01 pm
is it possible to limit the number of errorlog files to 2 ?
October 11, 2014 at 1:04 pm
charipg (10/11/2014)
is it possible to limit the number of errorlog files to 2 ?
Nope. Minimum number to configure is 6. You can delete all the archived errorlog files from your server if you want but I would ensure they are not required for auditing purposes and such.
You might want to set it to 6 and then create a scheduled job that simply calls "EXEC sp_cycle_errorlog". The more often you run this the smaller error log files you will have and will keep it to 6 error log files.
You can help clean up message by reviewing what messages are appearing. For example if it is "successful backup" messages you can enable trace flag 3226 globally for that instance and this will suppress those messages from being written all the time. Outside of that it is up to you to determine what is writing the message and figure out how to clean that up. An example of this that is most common is "failed login" messages for rogue service or application on a remote server.
Shawn Melton
Twitter: @wsmelton
Blog: wsmelton.github.com
Github: wsmelton
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply