Before you configure Universal Contact Server Manager to archive and prune data, consider the following points:
Leave at least two days of history in the database to calculate report metrics properly.
Allow Stat Server to access data before archiving or pruning the data. For example, if Stat Server calculates report metrics once a week, then archive or prune statistics that are at least seven days old.
To prevent problems with application performance, schedule database archiving/pruning and eServices reports at different times.
Note: If not configured correctly, data archiving and pruning could adversely affect the calculation of statistics used for eServices reporting.
For information on configuring Universal Contact Server, see the eServices Deployment Guide and the "Universal Contact Server Options" section in the "Configuration Options" chapter of the eServices Reference Manual.