Set the SQL Server Connection for the SQL Server Agent Service (SQL Server Management Studio)
This topic describes how to set the connection between SQL Server Agent and the Database Engine in SQL Server 2017 by using SQL Server Management Studio. The SQL Server Agent service can connect to a local instance of SQL Server by using Windows Authentication.
In This Topic
Before you begin:
To set the SQL Server Connection for the SQL Server Agent, using:
Before You Begin
Limitations and Restrictions
Object Explorer only displays the SQL Server Agent node if you have permission to use it.
Beginning with SQL Server 2005, SQL Server Agent does not support SQL Server Authentication. This option is available only when you administer an earlier version of SQL Server.
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 set the SQL Server connection
In Object Explorer, click the plus sign to expand the server that you want to set up with a connection to its SQL Server Agent Service.
Right-click SQL Server Agent and select Properties.
In the SQL Server Agent Propertiessever_name dialog box, under Select a page, click Connection.
Under SQL Server connection, select Use Windows Authentication to enable SQL Server Agent to connect to an instance of the SQL Server Database Engine with Microsoft Windows Authentication. Connections to SQL Server 2005 and later databases require Windows Authentication.