Attaching an archive allows you to view audited events that have been moved to an archive database. When you attach an archive, the Collection Server loads the database so you can view and report on the events. The audited events remain in the archive database, allowing you to manage the archived events without impacting the Repository databases.
By default, SQL compliance manager automatically attaches an archive when the corresponding database is created. If you are not reporting on audit data contained in an archive, consider detaching the archive to prevent unwanted access. When you detach an archive, SQL compliance manager continues to audit the associated SQL Server instance and databases.
When you attach an archive database generated with an earlier version of SQL compliance manager, you can choose whether to update the database now or schedule a time off-hours. Updating the archive database allows you to take advantage of performance enhancements, such as optimized indexes.
To attach archives:
- Select the SQL Server instance you want to attach an archive from the Explore Activity tree.
- Click File on the menu bar, and then select Attach Archive Database.
- Specify the appropriate settings, and then click OK.