Overview of the MOM Reporting Database
The MOM Reporting Database provides a location for storing long-term operations data for reporting and trend analysis.
When installed on a separate computer, it avoids the performance problems that are created when reports run directly against a MOM operations database.
The reporting database extends the SDK views included in MOM 2000 SP1, providing access to more of the operations data collected by MOM.
Reporting Database Security
Two Windows user groups, with associated SQL roles, manage access and security to the reporting database:
- SC DW Reader: has permission to read the SQL views in the reporting database and to run a small number of stored procedures. User accounts or applications that will use the reporting database should be added to the SC DW Reader Windows user group. You can also add a Windows user account to the SQL database users, and then add their SQL user to the SC DW Reader SQL role.
- SC DW DTS: this groups is used by MOM used when updating the contents of the reporting database. It has read privileges in the MOM operations database, and read-write privileges in the reporting database. It should not be used by users or applications that query the reporting database.
Upgrading Existing Reports and Extensions
Reporting solutions that used the MOM 2000 SP1 SDK views can be modified to run against the MOM 2005 reporting database, since the reporting database includes an equivalent set of views with the same names and columns. In most cases, only two changes are required:
- Change the server name in the SQL connection string, if necessary.
- Change the database source name from OnePoint to SystemCenterReporting.
- Add user accounts associated with reporting to the SC DW Reader user group.
There is no solution offered for migrating Access-based reports from previous versions of MOM to MOM 2005.