![sql server management studio 2018 sql server management studio 2018](https://www.mex.com.au/Content/Images/Blog/2020/BackingUpDatabaseSSMS2018_clip_image004.jpg)
SQLAgentReaderRole includes all the SQLAgentUserRole permissions as well as permissions to view the list of available multiserver jobs, their properties, and their history. It has permissions on only operators, local jobs, and job schedules. SQLAgentUserRole is the least privileged of the SQL Server Agent fixed database roles. If you have found some more causes, please share it with others via comments.īesides admin, there are other roles that will allow you to view the sa, each having different levels of access These are the only two reasons I found due to which you won’t see Agent node in SSMS. If above returns “Express” or “Express Edition with Advanced Services”, then you would not see SQL Server Agent node in SSMS.
![sql server management studio 2018 sql server management studio 2018](https://i.stack.imgur.com/NsxuZ.png)
To verify, you can run below query in SQL Server Management studio and check the output. Typically, SQL Server Express edition could be another cause. Another possible reason would be that SQL Server in not an edition which supports SQL Server Agent.If a value is zero, then you are not a Sysadmin and hence you can’t see SQL Server Agent. To verify, you can run below query in SQL Server Management Studio and check the output. If the Login account connecting to SSMS is not a part of SysAdmin role in SQL Server, then SQL Server Agent would not be visible?.As the title says – SQL Server Agent is missing in the second image. If you look closer at two SSMS connection. What could be the possible cause? I was able to provide him answers and sharing it here. He informed that he is not able to see SQL Server Agent node in SQL Server Management Studio (SSMS). While doing my recent Comprehensive Database Performance Health Check my client asked an interesting question. Learning never stops when you are a consultant.