Database partitioning

Use of partitioned database tables is an extra database configuration option for IBM® Sterling Control Center Monitor. IBM Sterling Control Center Monitor supports daily partitioned database tables. This eliminates the need to a set of production database tables and a set of staging database tables. When partitioned database tables are used, data is no longer moved to the staging database. Partitioned database tables allow archiving of production data without interfering with IBM Sterling Control Center Monitor normal operations. Entire data partitions (along with their indexes) are removed when the data meets its aging requirement, removing the requirement for periodic rebuilding of indexes.

Partitioned database tables are not apparent to IBM Sterling Control Center Monitor. The data on all active partitions is available to both reports and queries. IBM Sterling Control Center Monitor implements database partitioning in so that there is a separate partition for each day’s data. To provide for monitoring servers whose clock is not set properly, IBM Sterling Control Center Monitor ensures that partitions are defined to hold data up to 30 days in the future from the clock. As data is collected from the monitored servers, the database automatically puts the data into the appropriate partition based on the date/time of the event. When data is older than the value specified in System Settings, entire data partitions, including their indexes, are removed, rather than deleted row by row.

A migration path is provided to keep the staging data visible from a previous IBM Sterling Control Center Monitor database configuration when you are upgrading to the use of partitioning.

Using partitioned database tables allows IBM Sterling Control Center Monitor to support larger monitoring environments, to collect more data efficiently, and to provide for 24x7 operations.