Create and configure the Purge App job to periodically remove index, email, reporting, detail, annotation, dispute, and PWC data from the database. Running the Purge App job frees up space on your database server.
If your application calls for a certain number of month's statements to be included in a statement summary page, you must regularly run a Purge App job to eliminate index references to old statement data to prevent it from being included in summary page indexed fields.
If you upload detail to the database using the Detail Extractor job, or track annotations and disputes, run Purge App to remove this data as well.
Purge App also purges any sub-document index data when purging the data for its parent, or root document.
To prevent older statements from inclusion in the a summary screen, you must
· Run a Purge Apps job to remove the index references to the data input files that fall outside a specified date range.
· Remove the data input file (if not accessing from primary storage/backup location).
See Creating and Configuring a Purge App Job for details.
You can also use Purge Logs to clean up a testing or QA machine that has logged data you don't want or need; see Creating and Configuring a Purge Logs Job.