SQL SERVER Agent Missing from SSMS

Agent XPs can explain why SQL Server Agent is Missing from SSMS. I check edition and service state before changing configuration.

SELECT SERVERPROPERTY('Edition') AS Edition;
SELECT name,value,value_in_use FROM sys.configurations WHERE name=N'Agent XPs';
-- Administrator-approved Agent XPs change on a supporting edition:
-- EXEC sys.sp_configure N'show advanced options',1;
-- RECONFIGURE;
-- EXEC sys.sp_configure N'Agent XPs',1;
-- RECONFIGURE;
-- Restore the original advanced-options setting if changed.

Express does not include SQL Server Agent. Azure products have their own capabilities. Client updates and Agent XPs can’t supply a service absent from the edition.

On supported instances, inspect service state, permissions and effective Agent XPs. Object Explorer needs those procedures to expose Agent contents. Starting Agent through SSMS enables them automatically. Changing Agent XPs does not require an engine restart.

The commented template includes RECONFIGURE. Identify the cause before enabling it; the option does not itself start the service. Refresh or reconnect after correction and verify intended jobs and access.

Reference: Agent XPs and Object Explorer.

Related reading

• Comprehensive Database Performance Health Check
• Foundations of Document Databases with MongoDB – Video Course
• SQL Terms vs MongoDB Terms
• MongoDB Compass – Missing a Schema Section
• Getting Started With mongosh: Databases, Collections and Documents
• MongoDB insertOne and insertMany: Adding Documents the Right Way
• MongoDB find: Filters, Projections and Sorting for SQL People
• MongoDB updateOne: $set, $inc and Upserts Without Surprises
• MongoDB deleteMany: The Empty Filter That Deletes Everything
• SQL to MongoDB: Mapping SELECT, WHERE, GROUP BY and JOIN

A configuration flag is not a missing service installation, it is one prerequisite within the supported edition and access model.

Published by Pinal Dave on SQLAuthority. More of my work at pinaldave.com.