Cycle SQL Server Agent Error Log programmatically

Flipping on to next page

As many of us know it is possible to cycle the SQL Server Error Log without restarting the SQL Server using sp_cycle_errorlog. Does this take care of cycling the SQL Server Agent Error Log file (sqlagent.out)? No it does not. Is there a way to cycle the SQL Server Agent Error Log file?

In SQL Server 2000, there is no option to cycle the Agent Error Log file using T-SQL. The only option is to  restart the SQL Server Agent service. Starting SQL Server 2005, a new stored procedure has been introduced which addresses this issue. sp_cycle_agent_errorlog stored procedure takes care of cycling the SQL Server Agent Log file without restarting the Agent service.

USE msdb
go
EXEC sp_cycle_agent_errorlog
GO

We may not need this stored procedure very often, but it will come in handy when the sqlagent.out file grows really *big* and there is a need to keep it smaller.

Related posts:

  1. Quickly search through the Error Log
  2. SQL Server Agent does not start | StartServiceCtrlDispatcher failed (error 6)
  3. Cannot access Agent Jobs when SQL Service is restarted
  4. SQL Agent does not start | Login failed for user sa
  5. Run PSSDiag through a SQL Agent job

One thought on “Cycle SQL Server Agent Error Log programmatically”

  1. Pingback: Tweets that mention Cycle SQL Server Agent Error Log programmatically | SQL Server DBA Diaries of Pradeep Adiga -- Topsy.com

Comments are closed.