Performance Tuning Guide - EMC Community Network

Maintaining the Repository and BAM Databases
Purging and archiving the database
Performance problems can result from BAM database tables that grow quickly in high volume
applications. The rate data accumulate depends on the number of active processes, the number of
auditable events, and the number of data objects monitored by BAM, written to the BAM database
and extracted for the BAM dashboard.
Develop a strategy for purging the BAM database. What to purge and how often to purge depends on
how quickly the BAM database fills up and how long data must be retained for reporting purposes.
(See the BAM Implementation Guide for details.)
Note: Properly indexed tables can retain more data before affecting performance and requiring
maintenance.
Applying retention policies
Define a retention policy to archive or purge historical data from the database. The DBA manually
executes a retention policy or sets the retention policy to execute automatically by scheduling
jobs. The retention policy for aggregation tables can be less aggressive than for execution tables as
aggregation tables grow more slowly.
Purging the entire database
Periodically generate a dump file of the BAM database, then purge the entire BAM database. If
necessary, historic data can be restored. Depending on business need and the volume of process data,
create a snapshot (a dump file) of the BAM database every three or six months.
Purging selective portions of the database
Selectively purge large execution and aggregation tables of data that operational reports no longer
need. The BAM database provides instance level tables and nine types of aggregation tables. Over the
course of a single day, for example, the 5-minute aggregation table can hold 288 rows, 2016 rows over
a week, and 105,210 rows over a year. After a few months, the 5-minute aggregation data becomes
irrelevant, so purging this table every six months make sense. The same can be said of the 15-minute
aggregation table, although this table holds less data than the 5-minute aggregation table, with 35,040
rows per year compared to 105,210 rows for the 5-minute aggregation table.
EMC Documentum xCP 1.0 Performance Tuning Guide 87