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.
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.
Security
Permissions
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)
Administer an SQL Server database infrastructure for cloud, on-premises and hybrid relational databases using the Microsoft PaaS relational database offerings.
This article describes an error message that typically occurs in SSMS when there is a problem retrieving information about one or more databases of a SQL Server instance.