This window allows you to set the age at which audited events are archived, configure how the archive databases are partitioned and named, and schedule archiving to run automatically. You can continue to report on all audited events that you archive. SQL Compliance Manager uses these settings each time you archive audited events collected for a registered SQL Server instance.
Allows you to configure the following options to control which audit data is archived:
You can also skip the integrity check SQL CM usually performs before archiving your collected events. If the audit data for the selected SQL Server instance fails this integrity check, SQL CM does not archive the data.
Allows you to configure the following options to control when archiving runs:
Archive Database Creation
Allows you to configure the following options to control how the archive database is created:
By default, the Collection Server creates a new archive database at midnight (GMT) when the specified time period (month, quarter, year) ends. For example, if you set archive creation to occur every month, the Collection Server creates a new archive database at midnight on the first day of each month. Each archive database represents a separate data set. You can report on audited events from each archive database.
|Idera Website||Products||Purchase||Support||Resources||Community||About Us||Legal|