When you archive audit data, the Collection Server moves audited events from the Repository (typically, the event database) to an archive database. IDERA SQL Compliance Manager creates an archive database for each registered SQL Server instance, according to the file naming conventions and event age limit you specify. Each archive database contains events collected from the audited databases hosted on the SQL Server instance. You can archive event data across all registered SQL Server instances or for a selected instance.

To ensure you are archiving uncompromised audit data, SQL Compliance Manager allows you to check the integrity of the collected events. If the audit data fails this integrity check, SQL Compliance Manager does not archive the data.

During the archival process, the audited events are temporarily written to the tempdb before they are stored in the appropriate archive database. If you are archiving a large number of events, such as one million events, the tempdb may run out of available space, resulting in an incomplete archive.

To ensure optimal event handling and performance, archive your audit data frequently. Monitor your Repository database consumption over the first few days of collecting audit data, so you can develop a maintenance strategy that best suits your needs. For more information, see Back up and restore archive databases. For more information about archiving events, see Archive collected events.

Also consider grooming older audit data. Grooming allows you to minimize your storage requirements and ensure your audit data remains relevant to your compliance needs. For more information, see How grooming works.



IDERA |  Products | Purchase | Support |  Community | Resources |  About Us | Legal
  • No labels