Eagle Performance has three different types of tables in PERFORMDBO that should have a purge and archive strategy identified: audit tables, data tables, and results tables.
- Audit tables
- Data tables
- Results tables
| Anchor | ||||
|---|---|---|---|---|
|
...
This table stores the audit history of any time performance is committed. If you are going to purge or archive this table, you can do so by UPDATE_DATE so the most recent year or six months is available. If you archive, you can always get the data back if an audit question arises.
Note: | Be aware that if you archive the associated record in this table, you cannot finalize or un-finalize performance using the Commit Journal. |
| Anchor | ||||
|---|---|---|---|---|
|
...
This table stores the data records for each entity that relate each security to that entity. This table should only be populated with one record for each security the portfolio has ever owned, so it likely does not need to be purged or archived.
| Anchor | ||||
|---|---|---|---|---|
|
The results tables are currently specific to Retail Fund Performance. You can purge or archive these tables based on the results you require. The data tables are described as follows.
...
This table stores the child data records related to each parent record in MFP_AUDIT. Use AUDIT_ID to archive any child records in this table that are related to an archived parent record in MFP_AUDIT.