When should I upgrade?
SRP-9813: SQL Monitor now only suspends performance-related and custom alerts during maintenance windows. All other alerts continue to be raised as normal
SRP-9817: Changed the “Job failed” alert to “Job failing”, and changed the alert type from Event to Continuous. It will be automatically marked as Ended when the job runs successfully again, or when the job runs again and fails (in which case the original alert will be marked as Ended and a new alert will be raised)
SRP-10231: You can now configure the following alert types by time threshold:
Monitoring error (host machine data collection)
Monitoring stopped (host machine credentials)
Monitoring error (SQL Server data collection)
Monitoring stopped (SQL Server credentials)
Availability group - database not healthy
Availability group - listener offline
Availability group - not ready for automatic failover
Availability group - replica not healthy
SRP-10252: SQL Monitor no longer crashes if you change or disable the password for the account used to connect to the monitoring service (base monitor)
Updating to version 5.0.3 involves a SQL Monitor schema upgrade. We recommend you back up the data repository database before you update to version 5.0.3.
Now uses .NET Framework 4
When you add a cluster, SQL Monitor now monitors all standalone instances on nodes in the cluster, as well as failover cluster instances.
If you add new instances or nodes to a cluster that you’re already monitoring, SQL Monitor will automatically detect and monitor these additions.
If you're already monitoring a specific node within a cluster, and the cluster contains availability groups that you want to monitor, you’ll need to re-add the cluster when you upgrade to SQL Monitor 5. Otherwise, SQL Monitor won't detect and monitor these availability groups.
If you need to keep historical data from the cluster, make sure you don't remove the original cluster, even after you've re-added it. Instead, once you've re-added the cluster, you should suspend monitoring on the original cluster. This way, you can retain all historical data on the old cluster, while collecting new data on the newly added cluster.