This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 54%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJS%3C/text%3E%3C/svg%3E)
We're running SCOM 2012R2 and have noticed that when our SQL Servers have their services stopped that they're not generating an Alert in the SCOM Console, even though the management pack is setup for this. We're currently running SCOM Server 2016 MP 7.0.0.0 and this is discovering our SQL servers / databases / agents / etc successfully. We've also checked and there's no overides for the respective SQL Services ie (SQL Server Agent Windows Service).
We've also ensured that in our testing the Startup was set to Automatic as otherwise the alerts would not be generated.
In a lab environment the SQL 2016 7.0.15.0 was loaded on a SCOM 2019 server and we were able to successfully generate an alert once the sql service had stopped.
Please advise why in SCOM 2012R2 with SQL 2016MP:7.0.0.0 we're not getting alerts generated when a respective Automatic SQL Service is stopped.
Thanks,
Jason