| title | sp_cycle_agent_errorlog (Transact-SQL) | Microsoft Docs | ||
|---|---|---|---|
| ms.custom | |||
| ms.date | 03/14/2017 | ||
| ms.prod | sql | ||
| ms.prod_service | database-engine | ||
| ms.reviewer | |||
| ms.technology | system-objects | ||
| ms.topic | language-reference | ||
| f1_keywords |
|
||
| dev_langs |
|
||
| helpviewer_keywords |
|
||
| ms.assetid | 8aa96182-60b7-4d7b-b2a7-ccce70378c6e | ||
| author | stevestein | ||
| ms.author | sstein |
[!INCLUDEtsql-appliesto-ss2008-xxxx-xxxx-xxx-md]
Closes the current [!INCLUDEssNoVersion] Agent error log file and cycles the [!INCLUDEssNoVersion] Agent error log extension numbers just like a server restart. The new [!INCLUDEssNoVersion] Agent error log contains a line indicating that the new log has been created.
Transact-SQL Syntax Conventions
sp_cycle_agent_errorlog
0 (success) or 1 (failure)
None
Every time [!INCLUDEssNoVersion] Agent is started, the current [!INCLUDEssNoVersion] 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 [!INCLUDEssNoVersion] Agent error log.
USE msdb ;
GO
EXEC dbo.sp_cycle_agent_errorlog ;
GO