The OpsMgr 2007 management pack for SQL Server has been updated and was released to the MP Catalog on 10/29/2008 (version 6.0.6441.0). All MPs are supported on OpsMgr 2007 RTM and SP1. The table below is an excerpt from the MP guide detailing the changes and fixes that were made in this release. I’d especially like to point out the following:
Changes in This Update
SQL Server Management Pack version 6.0.6441.0 includes the following changes:
· The management pack now includes the SQL Server 2008 discovery and monitoring management packs. SQL Server 2008 monitoring is identical to the SQL Server 2005 management pack, including the new functionality added in this release for SQL Server 2005 monitoring.
· Addressed issues with a few performance rules attempting to collect performance counters or instances by the wrong name
· Updated a number of discoveries, rules, and tasks to ensure they use the correct RunAs profiles for discovery and monitoring.
· Updated the criteria on a number of event-based rules to make their criteria more specific to reduce alert volumes.
· SQL DB Engine discovery will now work on systems that do not have the SQL tools installed.
· The SQL Server 2005 and SQL Server 2008 management packs support discovery and partial monitoring of 32-bit instances of SQL components installed on 64-bit operating systems. This is discussed in more detail in the “Supported Configurations” section of this guide.
· All monitors are now set to public accessibility, allowing increased customization. Most notably, custom diagnostics and recoveries can now be added.
· The “Database Size” and “Log Size” properties of databases are now available as a numeric property, in addition to the string form of the property that already existed.
· Updated knowledge for various reports.
· Database snapshots are no longer discovered and monitored as if they were a full-fledged database.
· The possible states of the “Blocking SPIDs” monitor in all management packs have been changed to better align with the default override behaviors. Previously, the monitor could either be in a “Success” or “Warning” state. The “Warning” state has been replaced with “Error”.
Changes to the SQL Server 2000 Management Pack
· The default thresholds for the “Job Duration” have been revised. The numbers were previously an integer corresponding to minutes when it should have been in the format of HHMMSS. The knowledge for this monitor has been updated to more clearly explain the format of the threshold.
· Changed the frequency at which the SAPasswordMonitor.vbs script is run from 24 seconds to 24 hours.
Changes to SQL Server 2005 Management Pack
· Added monitoring for log shipping with the “Destination Log Shipping Monitor” and “Source Log Shipping Monitor” monitors.
· Fixed a few typos and formatting issues with product knowledge in various places.
The Operations Manager Team Blog just announced that version 6.0.6441.0 of the SQL Management Pack has
A new version of the SQL Server Management Pack is available for download:
Can we now install SCOM agents successfully on active/active SQL 2005 clusters or dooes this MP in combination with the newest Cluster MP still have trouble dealing with active/active setups?
Does anyone know when we will be able to integrate the native SCOM reports with SQL 2008.
Does anyone know when we will be able to integrate the native SCOM reports with SSRS 2008.
545 articles were published across 203 Microsoft Team blogs between the 20 th October and 2 nd November