Cycle SQL Server Error Logs based on size using PowerShell This is an off-site link.  Please review our Terms of Service for additional information.

(Jeffery Yao) The SQL Server error log is notorious for growing really large when certain things happen; like repeated login failures, stack dumps or other errors. In cases when trace flag 3226 is not turned on and there are hundreds of databases being backed up the error log can also grow really big.

Read this article...

comments powered by Disqus