Setting Up Archive Database
QAD recommends that you create a separate archive database and archive the audit trail data to this database. There are several reasons to do this:
• Audit trail data requirements grow over time, requiring more disk space. Having a separate archive database prevents audit trail data from taking disk space in the application database.
• Running audit reports against the application database will impact system performance.
• The archive database can be deployed in a flexible way.
• The archive database can store audit trail data from different application databases and act as a central reporting database.
Creating Optional Archive Database
The optional archive database is a copy of the empty database with auditing enabled. No other schema needs to be loaded. This database is used only for reporting and is optional.
To create an optional archive database, do the following steps:
1 Create an empty database:
prodb <db-name> empty
3 Log in to the database, create a user, and set privileges:
pro <db-name>
Access Progress Data Administration: choose Tools|Data Dictionary and press Enter. Next, choose the Admin|Security|Edit User List menu and create a user and password. Grant Audit Administrator and Audit Data Archiver privileges to this user. Save the settings and exit. (For further information, refer to the Progress documentation.)
5 Use the template scripts in the QAD Enterprise Applications installation directory to load archived audit trail data.