Microsoft has released another new update to the SQL management pack for Operations Manager 2007. The download page says nothing about what is new or fixed. My advice is simple: steer clear for a while and watch the forums/blogs. The last time I updated the SQL management pack I had a flood of false alarms due to bugs in the management pack. Once you’re ready for it, deploy it in a lab and see if you get alerts for no reason. Then deploy it on live, ideally when things are quiet and with lots of notifications so people are aware there could be critical alerts that are cause by bugs.
I’m not alone when it comes to being critical of the SQL management pack. The quality control hasn’t been great and it’s very public.
The OpsMgr bog announced the fixes in this management pack. These are:
- "Fixed performance issues caused by excessive CPU utilization and script timeouts from Windows Management Instrumentation (WMI) queries in the following management pack discoveries: Discover SQL Server 2005 Database Engines (Windows Server), Discover SQL Server 2005 Reporting Services (Windows Server), Discover SQL Server 2005 Analysis Services (Windows Server), Discover SQL Server 2008 Database Engines (Windows Server), Discover SQL Server 2008 Reporting Services (Windows Server), Discover SQL Server 2008 Analysis Services (Windows Server).
- Fixed an issue where SQL Server 2005 and SQL Server 2008 Analysis Services and Reporting Services discoveries were not reliably discovering these objects on instances of SQL Server that did not have the Database Engine installed.
- Removed the hard-coded exception in rules and monitors that prevented the monitoring of the System, Temp, and Master databases.
- Improved the means by which database discoveries recognize auto growth enabled settings. Database discoveries now recognize both “KB” and “%” growth settings; previously the database discoveries recognized only the “KB” growth setting".
Corrected typographical errors in product knowledge and improved the quality of the text.