Best Practice Alert: Run Kronos Workforce Record Manager (WRM) on its own application server, not on the production application server. This minimizes the impact WRM has on the performance of the production system. It also allows maintenance of the archive database to be performed outside of the Kronos production system's tight maintenance window.
Keep in mind that after years of data have been archived, the archive database will contain much more data than is stored within the production database, therefore, database maintenance activities on the archive database will take longer than such activities on the production database. Run Workforce Record Manager in your system's maintenance window or, if the maintenance window is too small, during off-peak hours.
Note: Kronos Workforce Record Manager allows pauses and resumes to be scheduled so you can limit its activities to a prescribed timeframe. Pauses and resumes are not instantaneous, so you should allow a window of several minutes (10-15 minutes is a good rule of thumb) to allow in-process work units to complete.
If you choose to start using WRM right away:
After each pay period, payroll lock the pay period and use the WRM copy option to copy the pay period's data from the production database to the archive database. Note: You will need to populate the copy start date value on the Copy Screen for the initial copy. To ensure all ancillary data gets copied, first go to the Archive Screen or the Purge Screen to see the pre-populated start date value. This value is determined by Workforce Record Manager by examining the dates of key records (usually accrual transactions) within your Kronos Workforce Central database. Populate the copy start date value with this same value.
At the end of a year (or whatever timeframe your company chooses to keep within the production database), use Workforce Record Manager to purge the data from the oldest pay period within the production database.