Yes, it is possible to archive audit data across multiple databases into a single reporting/archive database. A central architectural feature incorporated into OpenEdge Auditing is the merging of audit information from multiple databases into a single long term storage database.
Archiving Audit data is recommended as a best practice to avoid overgrowing a production database.
The primary key for the audit trail is a unique UUID, which allows audit information records to be generated from different sources without conflicts, the remaining indexes are non-unique as there can be duplicates in a valid audit information storage database. The main purpose for the _aud-audit-data._Audit-data-guid field is to provide a foreign key for the child table _aud-audit-data-value that is used to store individual, modified, field values for database events. This _Audit-data-guid field is also globally unique which allows Audit data to be archived from multiple databases to a central database, without comprising the integrity of the data. For further information the _Audit-data-guid is described in:
Progress OpenEdge Data Management, Core Business Services -Security and Auditing: "Audit Data Table Schema"
