Best Practice for database size and when to perform a purge in ARCS?
Summary:
Per the Oracle documentation, ARCS Administrators can help keep the size of the database in check and help performance by using archive, restore, and purge functionality. This allows Administrators to archive data and access the archived content as needed.
- Is there a way to view statistics of the ARCS database to see the size of the database?
- Are there any recommended database size parameters? I.e., what is considered a database size that is out of check/too large for good performance?
- Are there any best practices on when to perform a data purge in ARCS? For example, when the database reaches a certain size?
Tagged:
0