This topic describes how to set a Microsoft SQL Server alias for SQL Server Agent to use to connect to the Database Engine by using SQL Server Management Studio. By default, the SQL Server Agent service connects to an instance of SQL Server over named pipes by using dynamic server names that require no additional client configuration. You need to configure a server connection alias only if you are not using the default network transport or if you are connecting to an instance of SQL Server that listens on an alternate named pipe.
In This Topic
Before you begin:
Before You Begin
Limitations and Restrictions
SQL Server Agent will not work correctly unless you select an alias that refers to the local instance of SQL Server.
Object Explorer only displays the SQL Server Agent node if you have permission to use it.
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 a SQL Server Alias for the SQL Server Agent Service
In the Object Explorer, connect to an instance of the SQL Server Database Engine and then expand that instance.
Right-click SQL Server Agent, and then click Properties.
In the SQL Server Agent Propertiesserver_name dialog box, under Select a page, select Connection, and
In the Alias local host server box, type the alias of the server to which SQL Server Agent should connect.