| title | sp_cycle_agent_errorlog (Transact-SQL) | ||
|---|---|---|---|
| description | Closes the current SQL Server Agent error log file, and cycles the SQL Server Agent error log extension numbers. | ||
| author | markingmyname | ||
| ms.author | maghan | ||
| ms.reviewer | randolphwest | ||
| ms.date | 06/23/2025 | ||
| ms.service | sql | ||
| ms.subservice | system-objects | ||
| ms.topic | reference | ||
| f1_keywords |
|
||
| helpviewer_keywords |
|
||
| dev_langs |
|
[!INCLUDE SQL Server]
Closes the current [!INCLUDE ssNoVersion] Agent error log file and cycles the [!INCLUDE ssNoVersion] Agent error log extension numbers just like a server restart. The new [!INCLUDE ssNoVersion] Agent error log contains a line indicating that the new log was created.
:::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: Transact-SQL syntax conventions
sp_cycle_agent_errorlog
[ ; ]
None.
0 (success) or 1 (failure).
None.
Every time [!INCLUDE ssNoVersion] Agent is started, the current [!INCLUDE ssNoVersion] Agent error log is renamed to SQLAgent.1; SQLAgent.1 becomes SQLAgent.2, SQLAgent.2 becomes SQLAgent.3, and so on. sp_cycle_agent_errorlog enables you to cycle the error log files without stopping and starting the server.
This stored procedure must be run from the msdb database.
Execute permissions for sp_cycle_agent_errorlog are restricted to members of the sysadmin fixed server role.
The following example cycles the [!INCLUDE ssNoVersion] Agent error log.
USE msdb;
GO
EXECUTE dbo.sp_cycle_agent_errorlog;
GO