Skip to content

rename-a-sql-server-agent-error-log-sql-server-management-studio.md

Latest commit

 

History

History
65 lines (44 loc) · 3.71 KB

rename-a-sql-server-agent-error-log-sql-server-management-studio.md

File metadata and controls

65 lines (44 loc) · 3.71 KB
title Rename a SQL Server Agent Error Log
ms.custom seo-lt-2019
ms.date 01/19/2017
ms.prod sql
ms.prod_service sql-tools
ms.technology ssms
ms.topic conceptual
helpviewer_keywords
logs [SQL Server], SQL Server Agent
renaming SQL Server Agent error log
SQL Server Agent, errors
errors [SQL Server Agent]
ms.assetid dee2b199-48af-44cb-9177-d029a5edb169
author markingmyname
ms.author maghan
ms.manager jroth
ms.reviewer
monikerRange = azuresqldb-mi-current || >= sql-server-2016 || = sqlallproducts-allversions

Rename a SQL Server Agent Error Log

[!INCLUDEappliesto-ss-asdbmi-xxxx-xxx-md]

Important

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 [!INCLUDEmsCoName] [!INCLUDEssNoVersion] Agent errors are written in [!INCLUDEssCurrent] by using [!INCLUDEssManStudioFull].

Before You Begin

Limitations and Restrictions

  • Object Explorer only displays the [!INCLUDEssNoVersion] Agent node if you have permission to use it.

  • [!INCLUDEssNoVersion] Agent will not write to the new log file until the [!INCLUDEssNoVersion] Agent service is restarted.

Security

Permissions

To perform its functions, [!INCLUDEssNoVersion] Agent must be configured to use the credentials of an account that is a member of the sysadmin fixed server role in [!INCLUDEssNoVersion]. 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 [!INCLUDEssNoVersion] 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

  1. In Object Explorer, click the plus sign to expand the server that contains the [!INCLUDEssNoVersion] Agent error log that you want to rename.

  2. Click the plus sign to expand SQL Server Agent.

  3. Right-click the Error Logs folder and select Configure.

  4. 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.

  5. When finished, click OK.