A configuration archive is a snapshot of the configuration parameters of a registered data source. You use a configuration archive in configuration comparisons against other data sources, standards, and archives to monitor property values and provide backups.
You can periodically update archives with the current values of an associated data source to create new versions. Older versions are retained with an archive and can be recalled as needed.
Archives are listed in Data Source Explorer under their corresponding data source. The following tasks step you through creating a configuration archive:
You create or modify a configuration archive in the Configuration Archive editor. For more details about the editor, see Configuration Archive Job Editor.
To create a new configuration archive job
To open an existing configuration archive job
The Archive Name and Description pane contains more than just the Name field. It shows where the job is stored in Project Explorer. When you click the Details button, you can see the project’s file directory path.
To describe a configuration archive job
The configuration Archive Source table specifies the data source from which the archive is derived.
To specify and save a configuration archive source
When you create a new archive, by default all data source properties are included. However, you may choose to archive only a specific group of properties. For example, you may want to define an archive that retains only the security properties of the associated data source.
You can create multiple archives for the same data source. For example, another archive may retain only the performance properties.
Archive configuration properties are listed on the Refinements tab of the Archive Job editor.
To specify configuration archive properties
Within the same archive, properties are retained across versions unless you specify new values.
Each time you create a new archive, DB Change Manager includes all properties of the specified data source and you must again refine the properties. |
When an archive job completes, DB Change Manager provides various ways of notifying you. For more information, see Setting job notifications.
The Options tab in the Configuration Archive Job editor contains options for handling the DDL and purging older archives.
If you select the Extract DDL option, the synchronization code produced by the job comparison will appear in a separate editor window when the comparison is done.
The Automatic Purge Options delete archive files after a number of days, number of versions, and/or when the size of the files reaches a certain limit. The purge conditions are checked and enforced when an archive job is saved or when a new version is created.
To specify the conditions for automatically deleting archives
When you first run an archive job, DB Change Manager creates the first version of the archive. A version stores snapshots of the same archive job for backup or tracking comparison purposes. Versions are listed in the Archive Job History table on the History tab and in the Data Source Explorer.
To create a version and save a configuration archive job
You create additional versions within the same archive job each time you click Run Job. The new version contains the latest values for the archive job properties as specified on the Refinements tab.
To open an archive version
After running a comparison job, you can create a job report using the View Report button on the Results tab. For more information, see Creating a job report.
You can use a configuration archive in configuration comparison job the same way as registered data sources or standards.
To add a configuration archive to a configuration comparison job
For more information, see Comparing database configuration settings.
| | | | | | | |