Since this is one of those configurations which it’s difficult to work through in a lab (even thought it is documented in the SQL management pack guide) , the following is a screen by screen view of enabling SQL Replication Monitoring in Operations Manager.

Prior to enabling this functionality, the SQL management pack replication section looked like the following: (no information existed on any of the replication state views shown below)


To enable this functionality we found which version of SQL each server has installed and then located the object discoveries for that version of SQL using the Microsoft SQL Server / Computers view and using the Look for option to locate each server.



As shown above for our environment, there were two SQL 2005 servers which we wanted to monitor their replication. Next we enabled these discoveries for the two servers for the Discover Replication Components for SQL 2005 Distributor object discovery shown below. We also attempted to enable the “Discover Replication Components” for SQL 2005 Publisher for the two systems (but this override already existed – it came from the one we created for the SQL 2005 Distributor). Finally we enabled the “SQL 2005 Replication Publications and Subscriptions Discovery Provider” for the two systems. These discoveries are configured to run every 4 hours by default but appear to run right after their override is created to enable the discovery. This process would be the same if we were enabling replication monitoring for SQL 2008 but would use the SQL 2008 equivalents of the SQL 2005 discoveries which we enabled here (“Discover Replication Components for SQL 2008 Distributor” and “SQL 2008 Replication Publications and Subscriptions Discovery Provider”).


Once we made this change we found objects in Distributor State (one went green one went unmonitored) and Publisher State (unmonitored). We first saw an item in the Distributor State (unmonitored) which eventually became monitored. Multiple items appeared as not monitored in the Publisher State (unmonitored). The Subscription State next appeared with an item as not monitored. Multiple items appeared as unmonitored in the Publisher State. Finally, as we review health explorer for these servers we can see how SQL Replication has been integrated into the health views. Each of these steps is shown in the images below.