Skip to content

configure-sql-server-agent.md

Latest commit

 

History

History
69 lines (45 loc) · 4.75 KB

configure-sql-server-agent.md

File metadata and controls

69 lines (45 loc) · 4.75 KB
title Configure SQL Server Agent
ms.prod sql
ms.prod_service sql-tools
ms.technology ssms
ms.topic conceptual
helpviewer_keywords
SQL Server Agent, configuring
accounts [SQL Server], SQL Server Agent
SQL Server Agent, permissions
security [SQL Server], SQL Server Agent
ms.assetid 2e361a62-9e92-4fcd-80d7-d6960f127900
author markingmyname
ms.author maghan
ms.manager jroth
ms.reviewer
ms.custom seo-lt-2019
ms.date 01/19/2017
monikerRange = azuresqldb-mi-current || >= sql-server-2016 || = sqlallproducts-allversions

Configure SQL Server Agent

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

Important

On Azure SQL Database managed instance, most, but not all SQL Server Agent features are currently supported. Enabling and disabling SQL Server Agent is currently not supported in SQL Database managed instance. SQL Agent is always running. See Azure SQL Database managed instance T-SQL differences from SQL Server for details.

This topic describes how to specify some configuration options for [!INCLUDEssNoVersion] Agent during installation of [!INCLUDEssNoVersion]. The full set of [!INCLUDEssNoVersion] Agent configuration options is only available within [!INCLUDEssManStudioFull], [!INCLUDEssNoVersion] Management Objects (SMO), or the [!INCLUDEssNoVersion] Agent stored procedures.

Before You Begin

Limitations and Restrictions

  • Click SQL Server Agent in Object Explorer of [!INCLUDEssManStudioFull] to administer jobs, operators, alerts, and the [!INCLUDEssNoVersion] Agent service. However, Object Explorer only displays the [!INCLUDEssNoVersion] Agent node if you have permission to use it.

  • Auto-restart should not be enabled for the [!INCLUDEssNoVersion] service or the [!INCLUDEssNoVersion] Agent service on failover cluster instances.

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 configure SQL Server Agent

  1. Click the Start button, and then, on the Start menu, click Control Panel.

  2. In Control Panel, click System and Security, click Administrative Tools, and then select Local Security Policy.

  3. In Local Security Policy, click the chevron to expand the Local Policies folder, and then click the User Rights Assignment folder.

  4. Right-click a permission that you want to configure for use with [!INCLUDEssNoVersion] and select Properties.

  5. In the permission's properties dialog box, verify that the account under which [!INCLUDEssNoVersion] Agent runs is listed. If not, click Add User or Group, enter the account under which [!INCLUDEssNoVersion] Agent runs in the Select Users, Computers, Service Accounts, or Groups dialog box, and then click OK.

  6. Repeat for each permission that you want to add to run with [!INCLUDEssNoVersion] Agent. When finished, click OK.