BRONZE PARTNER:
BRONZE PARTNER:
Industry News:
| |
| |
|
|
|
|
|
| MOM FAQ: Implementing a Second SQL Server to Archive MOM Performance Data |
|
|
|
By: Cliff Hobbs
Posted On: 1/31/2003
Problem
I need to implement a second SQL server to archive all of the Performance Data MOM collects in order to be able to produce performance report per month or week. Has anyone created a DTS package, to replicate MOM data to an off line SQL server for archiving purposes?
Contributed by David Williams
This is easily done by replicating the MOM database. If you’re going to decipher the database and use your own reporting engine, then that’s all you need. However, if you’re going to use MOM’s Reporting engine, then you’ll need to install some additional MOM components on that server as well.
There was a good Webcast by MS that went into this and lots of DB maintenance gotchas to keep the DB efficient. Check out the Support WebCast: Microsoft Operations Manager: How to Manage the MOM Database webcast
Note one thing - the original MOM database is going to experience sufficient increase in I/O with transactional replication. You may want to do merge replication instead to make snapshots.
We have an implementation where we simply backed up the database to file and restored in on another server.
I recently completed a project where we setup a data warehouse for a manufacturing company. The production databases from multiple locations were groomed to keep only 90 days worth of order production data in the various databases, but our client has to keep 7 years of history available at all times for legal reasons and for reporting. We ended up setting up nightly DTS packages to pull any new records from certain tables since the last pull and write it in the data warehouse DB. Since we only pull the data we wanted, the database stays fairly manageable.
We also threw in a bunch of indexes based on the reports that were going to run. So now when queries are run against these tables, most containing 100+ million rows, we get data back in seconds.
If you’re going to do serious reporting, this may be a good option for you.
We’re looking at doing the same thing for a security project that we’re working on. We’re only going to pull Security log events from the original MOM database. We want to keep 2 years of security data, so DTS seems like the natural way to handle this.
|
|
|
|
|
|
