Previous Topic: Which Tables Are Partitioned and Purged?Next Topic: Storage and Partitioning Procedure


Partitioning and Purging Features

Applicable to Oracle databases only

CA DataMinder support for database partitioning includes the following benefits:

Clear separation between core and customizable partitioning and purging features

All customizable purging and partitioning features are implemented in a separate database package from the core features that ship with CA DataMinder. This formal separation of customizable and core features makes them much easier to maintain. In particular, it ensures that any customizations made within the appropriate package body are not overwritten during subsequent upgrades or reinstallations of CA DataMinder.

For example, any future enhancements to core purging procedures provided by CA DataMinder can be easily rolled out to all customers without affecting any existing customizations already in use. Likewise, customers can add their own customizations in the future without affecting core purge and partitioning functionality.

Create timestamp-based partitions

The CA DataMinder database schema provides support for table partitioning based on event time stamps. For example, you can set up 7 day or 30 day partitions.

Configure partition-based purging

Partition-based purging is dramatically faster than relying solely on infrastructure-based purging. After setting up partitions, typically, you will set up a purge strategy based on rolling partitions.

Handling for failed purges

If a partition-based purge fails to complete, you can use information recorded in the CMS database to locate and fix the problem, and then restart the purge (using a database function provided by CA DataMinder) from the point where it failed.