Skip to content

Latest commit

 

History

History
57 lines (40 loc) · 4.33 KB

configure-sql-server-agent.md

File metadata and controls

57 lines (40 loc) · 4.33 KB
title description author ms.author ms.date ms.service ms.subservice ms.topic helpviewer_keywords monikerRange
Configure SQL Server Agent
Configure SQL Server Agent
markingmyname
maghan
01/19/2017
sql
ssms
how-to
SQL Server Agent, configuring
accounts [SQL Server], SQL Server Agent
SQL Server Agent, permissions
security [SQL Server], SQL Server Agent
= azuresqldb-mi-current || >= sql-server-2016

Configure SQL Server Agent

[!INCLUDE SQL Server SQL MI]

Important

On Azure SQL 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 Managed Instance. SQL Agent is always running. See SQL 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 SQL Server Management Studio, [!INCLUDEssNoVersion] Management Objects (SMO), or the [!INCLUDEssNoVersion] Agent stored procedures.

Before you begin

Limitations and restrictions

  • Select SQL Server Agent in Object Explorer of SQL Server Management Studio 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.

To configure SQL Server Agent

  1. Select the Start button, and then, on the Start menu, select Control Panel.
  2. In Control Panel, select System and Security, select Administrative Tools, and then select Local Security Policy.
  3. In Local Security Policy, select the chevron to expand the Local Policies folder, and then Select 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, select 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 Select OK.
  6. Repeat for each permission that you want to add to run with [!INCLUDEssNoVersion] Agent. When finished, select OK.