Best practices for archiving

Infor highly recommends that you implement some level of baseline archiving after you deploy the application. This will prevent potential performance issues due to the database scanning tables with a large amount of records. For example, you may not be able to run payroll export because the database is scanning millions of records in a particular table. If you run archiving on a regular basis for heavily used parts of the product, you can avoid this type of situation. This section outlines a strategy for you to implement a basic level of archving which you can adjust to meet your own needs.

It is also necessary to monitor the results of the basic archiving recommendation in this section and adjust based on your specific requirements. You may need a DBA or someone that monitors your system health to monitor the archiving to ensure you do not archive records that are essential and required for your deployment. There may be records in your database that you really do not need after a week or two and can safely archive with an aggressive approach, while you may want to maintain records in other areas of the product for a long period of time. Archiving requirements in different environments, varying numbers of employees and different use cases will vary. It is your responsibility to implement and monitor the archiving requirements that are suitable for your organization.