Database Tutorials MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux 
In some cases, the SQL Server Error Log File grows very fast. And when the file grows too large, it becomes difficult to read.
Before you read this article, I suggest you read articles “How To Filter SQL Server Error Log(Like or Not Like)” and “How to Increase SQL Server Error Log File Count“.
Some DBAs are restarting the SQL Server Service to create a new Error Log file when the Error Log file is too large. Because a new log file occurs when SQL Server Service restarts.
Below you see Current is our current error log file. The date next to it is the date the file was created.
This means that; SQL Server Service restarted on 23.9.2016, or a person might have consciously created a new file. The subject of this article is to create a new file without restarting the sql server service.
We are performing the recycle process by running the following script.
1 2 | EXEC sp_cycle_errorlog GO |
When we right-click on SQL Server Logs and click refresh, we see that a new file is created. When I ran this script, it was 10:55.
If your SQL Server does not restart for a long time, you can convert this script to a job and run it once a month or once every 3 months. You can use the article titled “How To Create a SQL Server Job“
