Rename a SQL Server Agent Error Log (SQL Server Management Studio)
On Azure SQL Database Managed Instance, most, but not all SQL Server Agent features are currently supported. See Azure SQL Database Managed Instance T-SQL differences from SQL Server for details.
This topic describes how to rename the file where Microsoft SQL Server Agent errors are written in SQL Server 2017 by using SQL Server Management Studio.
In This Topic
Before you begin:
Before You Begin
Limitations and Restrictions
Object Explorer only displays the SQL Server Agent node if you have permission to use it.
SQL Server Agent will not write to the new log file until the SQL Server Agent service is restarted.
To perform its functions, SQL Server Agent must be configured to use the credentials of an account that is a member of the sysadmin fixed server role in SQL Server. The account must have the following Windows permissions:
Log on as a service (SeServiceLogonRight)
Replace a process-level token (SeAssignPrimaryTokenPrivilege)
Bypass traverse checking (SeChangeNotifyPrivilege)
Adjust memory quotas for a process (SeIncreaseQuotaPrivilege)
For more information about the Windows permissions required for the SQL Server Agent service account, see Select an Account for the SQL Server Agent Service and Setting Up Windows Service Accounts.
Using SQL Server Management Studio
To rename a SQL Server Agent error log
In Object Explorer, click the plus sign to expand the server that contains the SQL Server Agent error log that you want to rename.
Click the plus sign to expand SQL Server Agent.
Right-click the Error Logs folder and select Configure.
In the Configure SQL Server Agent Error Logs dialog box, in the Error log file box, enter the new file path and file name for the error log. Alternately, click the ellipsis (...) to open the Specify agent error log location dialog box.
When finished, click OK.