| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | helpviewer_keywords | monikerRange | ||
|---|---|---|---|---|---|---|---|---|---|---|---|
Choose the Agent Service Account for Multiserver Environments |
Choose the Right SQL Server Agent Service Account for Multiserver Environments |
markingmyname |
maghan |
01/19/2017 |
sql |
ssms |
how-to |
|
= azuresqldb-mi-current || >= sql-server-2016 |
[!INCLUDE SQL Server]
Important
On Azure SQL Managed Instance, most, but not all SQL Server Agent features are currently supported. See Azure SQL Managed Instance T-SQL differences from SQL Server for details.
The Windows account you choose for the [!INCLUDEssNoVersion] Agent service can affect the behavior of a multiserver environment, as follows:
-
If you run the [!INCLUDEssNoVersion] Agent service under an account that is not a member of the local Windows Administrators group, enlisting target servers to master servers may fail. If it does, the following error message is returned:
"The enlistment operation failed."
Restart the [!INCLUDEssNoVersion] and the [!INCLUDEssNoVersion] Agent services to resolve this issue.
-
When the [!INCLUDEssNoVersion] Agent service is run under the Local System account, master server-target server operations are supported only if both the master server and the target server reside on the same computer. If you use this configuration, the following message is returned when you enlist target servers to a master server:
"Ensure the agent start-up account for <target_server_computer_name> has rights to log on as targetServer."
You can ignore this informational message. The enlistment operation should complete successfully.
For more information about choosing an account for the [!INCLUDEssNoVersion] Agent service, see Select an Account for the SQL Server Agent Service.