MOM Operations Database SDK Views

  • Article

Overview

MOM includes several SQL views to help you create custom reports and transfer data from the MOM operations database to other applications and data stores.

SQL views simplify your queries by populating columns with data collected from multiple tables in the database. These views offer several advantages over querying the tables directly:

  • You do not need in-depth knowledge of the entire database or the relationship between tables and keys.

  • If the database structure changes in future versions of the product, the views can be updated so that they behave the same.

  • For MOM installations that use a separate, dedicated computer for the SQL Server database, the views are queried on the database computer, not the computer running MOM. This results in less competition for resources when large numbers of views are queried over a short period of time. Queries for MOM WMI objects are always processed by the computer running MOM, which can result in a potential conflict for resources with the other services on the server running MOM.

The potential disadvantages of the SQL views include the following:

  • Because the view runs each time it is queried, server performance will be degraded if the view is used too frequently.

  • The available supported views might not include all of the columns you need.

When to Use the SQL Views

Compared to the MOM WMI classes, the SQL views provide better performance when read-only access to the MOM data is required. This is especially true when the MOM database is on a separate, dedicated computer. The WMI classes should be used in situations where performance is not a priority and you need both read and write access to some of the object properties.

If long-term data is required, a MOM Reporting Database should be deployed and regularly updated with new data from the operations database. The Reporting Database schema includes views that are comparable to the SDK views in the operations database, making it easier to create queries and reporting tools that can work with both of these data sources.

Security and Access for the OnePoint Database SDK Views

Access to the OnePoint database SDK views is managed through the MOM SDK View User database role. To grant access to a Windows user account, you must add the account as a new database user for the OnePoint database, and then assign the MOM SDK View User database role to the database user.

The MOM SDK views are read-only. Changes to the MOM databases, such as adding tables, views, or fields, or modifying security settings are not supported.

Security and Access for the SystemCenterReporting Database SDK Views

The SDK views included in the SystemCenterReporting database use the same security as the other views in this database. For information about SystemCenterReporting database security, see Overview of the MOM Reporting Database.

SDK Views

The MOM OnePoint and SystemCenterReporting SQL Server databases support the following views:

The following illustration shows the SQL views and the associations between them.

 MOM SQL Views

Note Note   

The MOM OnePoint SQL Server database includes many views in addition to the ones listed above. Only the views with the SDK prefix should be used. The use of any of the other views is not recommended or supported. For the supported views in the SystemCenterReporting database, see the MOM Reporting Database Schema.

Database Grooming

MOM automatically manages the grooming of its database. The grooming rate depends on the size of the database and the amount of data collected by the rules. When querying any of the SDK views, keep in mind that the MOM database is used to support its monitoring and management functions and is not optimized for reporting. Particularly when creating reports that examine trends over time, keep in mind that the database represents only a partial record of the events and activity on the agent computers.

The topics and samples in the MOM SQL Views section assume you are familiar with relational database concepts and data access technologies, such as ActiveX Data Objects (ADO) and Open Database Connectivity (ODBC) drivers. For more information, see SQL Server and Transact-SQL Overview.

For more information about the SQL Server data types used in the MOM SDK views, see Data Types at MSDN Online. For information about how ODBC maps these SQL Server data types to Visual C++ data types, see SQL: SQL and C++ Data Types (ODBC). The Visual C++ MFC Class Wizard handles these type mappings automatically.

See Also

MOM Reference