Data retention is based off the date the history snapshot was created and is established during EOD. This date does not change. The data retention policy, however, can be revised from the default period.
When you revise the data retention period, the change is recognized the next time the Data Retention job runs.
Changing the retention policy has the following results:
- If you revise a data retention period for a shorter time period than is
currently used, for example, to run every 45 days instead of 90 days, the
volume of data marked for deletion during the next cycle will be higher
than usual and will require additional processing time.
- If you revise the data retention period for a longer time period than is
currently used, for example, from 90 days to 120 days, data already
marked for deletion will not be unmarked and will be purged during the
- For reconciliations, cash differences, and adjustments, the data retention
period is set in the Data Model Settings for the definition. Letter data
retention is based on the adjustment data retention period.
Recommendations for Data Retention and Cleanup
- The length of time it takes for the data retention and cleanup jobs to run
depends on the amount of data your system processes and the length of
your retention periods. In general, some suggestions to optimize data
retention and clean are to:
- Set the Start Time of both the Data Retention and Data Cleanup jobs to
something other than 2:00 a.m. to avoid daylight savings time issues.
- Schedule the Data Cleanup job to run only once a week.
In addition, because data cleanup and EOD are database intensive
operations, do not schedule them to run at the same time.
- For very large volumes of data, plan an adequate time window in which to
complete the data cleanup. This can only be determined by your volume of
data and the length of your data retention period