KMoody
Member
OpenEdge documentation recommends archiving auditing data separately from production databases. I'd like to get some clarification on the reasons why.
(Context: Our production databases are 4.8 GB, and our archive database is 10 GB. We are not legally bound to use auditing; for us, it serves as a log. Once a week, we archive auditing from production into a separate audit storage database on the same server. Once a month, we archive data older than three years from the audit storage database.)
Why is audit data in a production database at a high risk of data corruption over time? How does moving auditing data to a separate database prevent corruption?
Let's say we left auditing data in the production databases and activated all audit table indexes. If audit table indexes were in their own storage area, would auditing reports or the production databases' performance suffer?
Finally, given the sizes of our databases, why might we want to keep auditing separate from production?
Thanks for your help!
(Context: Our production databases are 4.8 GB, and our archive database is 10 GB. We are not legally bound to use auditing; for us, it serves as a log. Once a week, we archive auditing from production into a separate audit storage database on the same server. Once a month, we archive data older than three years from the audit storage database.)
Source: "It is, however, your choice whether or not to move the audit data. If the database size is not an issue, you might not want to move the data; however, the longer the audit data resides in a database along with the application data, the higher the risk of data corruption."
Why is audit data in a production database at a high risk of data corruption over time? How does moving auditing data to a separate database prevent corruption?
Source: "To keep your production database from growing too large too quickly, and for greater reporting capabilities (remember, Progress recommends only minimal indexing of the audit tables in your production database), you are going to want to archive your audit data to a long-term storage database "
Let's say we left auditing data in the production databases and activated all audit table indexes. If audit table indexes were in their own storage area, would auditing reports or the production databases' performance suffer?
Finally, given the sizes of our databases, why might we want to keep auditing separate from production?
Thanks for your help!