Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

DB Change Manager supports cross-platform schema comparisons. However, such jobs are limited to the following DBMS combinations and data source objects:

DBMS Source/TargetObjects Compared
Sybase / SQL ServerTables, Unique Keys, Check Constraints, Foreign Keys, Indexes, Primary Keys, Views
Oracle / SQL ServerTables, Unique Keys, Check Constraints, Foreign Keys, Indexes, Primary Keys, Views

If you attempt to compare two data sources that are not compatible, the Schema Comparison Job editor does not let you place objects in the Source or Target panes.

...

The Refinements Mapping table lists schema elements for the job source and target.

Image Added

By default, new objects are included in this list. For more information, see CM/Schema > Refinements Options.

When comparing master catalogs or user mappings, you can select multiple targets against a single source.

To redefine schema object mappings

  • In the Refinements Mapping tab, click the target of the pair you want to change. Use the drop-down menu to define the object you prefer.

To restore original schema object mappings

  • Click Restore Default Mappings to revert to the original object mappings as determined by DB Change Manager.

Specify Schema Comparison Job Options

Prior to running a job, you can set various options to control aspects of the comparison process. Set them using the Options tab.

The list of options differs depending on the DMBS of the source and target data sources. Options differ according to the objects included in the job. For example, Ignore Constraint Name Differences do not appear if you exclude constants from the job.

The options you see in the job have defaults. You can change the defaults using Preferences.

Schema comparison job options include:

  • Synchronization Options. These options specify how you want DB Change Manager to handle the synchronization script after it runs the comparison job, either:
    • Manual causes DB Change Manager to display the results of the comparison, but it does not automatically attempt to repair any synchronization issues. If you choose this option, you will still be able to manually generate and run a synchronization script after the job runs.
    • Automatic causes DB Change Manager to automatically generate and run a synchronization script immediately after the comparison job runs.
  • Include Object Options. These settings determine what elements of the job source and target will be omitted when running a schema comparison job and synchronization. For more information, see CM/Schema > Comparison Options > Include Objects Options.
  • Compare Options. These settings affect how objects are treated in the comparison process. You can include or exclude specific object types in the job, and specify the behavior of the comparison job and synchronization scripts. For more information, see CM/Schema > Comparison Options > Compare Options.
  • Decorator Options. These settings affect particular database objects. For more information, see CM/Schema > Comparison Options > Decorator Options.
  • Identifier Options. These settings determine what elements of the source and target data source will be ignored during the schema comparison and synchronization process. For more information, see CM/Schema > Comparison Options > Identifier Options.
  • DDL Extract Option. This setting causes the DDL code to appear in a separate editor window after the comparison job runs. For more information, see CM/Schema > Comparison Options > DDL Extract Options.
  • Custom Options. This section lists options that you defined in the Create New Schema Custom Compare Options dialog. For more information, see Select Schema Properties to Ignore During a Comparison

As needed, DBMS-specific options settings are also listed. For more information, see CM/Schema > Comparison Options > Additional Options.

Anchor
CloneJob
CloneJob
Cloning a schema comparison job

...