Archiving the Central repository database – ApexSQL Audit

This article describes how to archive ApexSQL Audit’s Central repository database, explains the background of the process, and how to use archived repositories for creating reports.

To archive the central repository database, use the Archive database option in the ApexSQL Audit menu

Before the process starts, the user is warned that it cannot be undone, or canceled once it’s started. To continue with the archiving process, confirm by selecting the Archive option; otherwise, select the Close option

The background of the archiving process

Archiving in ApexSQL Audit is accomplished by renaming the current repository (using the ArchiveCRD_yyyymmdd_hhmmss database name pattern) while keeping it on the same SQL Server instance. At the same time, a new repository (ApexSQLCrd database) is created to be used by the ApexSQL Audit service.

There is no actual copying of captured data from one database to another at the moment of archive creation, except for some basic internal system data (such as auditing configurations). This makes creating an archive quite fast, regardless of the size of the current repository. Additionally, to actually free up the disc space, you can detach the archive, move the archive database files to another partition (or machine) and reattach it.

Using archived repository database for creating auditing reports

After archiving the data will remain available for reporting. However, if the archived databases need to be moved to cold storage or otherwise detached from the server or there is need to exclude or include various archived databases from reporting data source management can be accessed in the reporting tab of ApexSQL Audit.