Schema Compare for Oracle - 3.0

Schema Compare for Oracle

Setting project options - Schema Compare for Oracle

Project options enable you to modify the comparison and deployment behavior of Schema Compare for Oracle.

For example, you can set a project option so that when you run a comparison, certain differences between two objects are ignored.

To set project options:

  1. Open the Project Configuration dialog box if it is not displayed.
  • If you want to set options for a new project, on the toolbar, click New
  • If you want to set options for a saved project, on the toolbar, click Open, select a project, and click Open
  • If you are reviewing comparison results for an open project, on the toolbar, click Edit Project
  1. On the Project Configuration dialog box, click the Options tab.

    The list of available options is displayed:

  2. For each option you want to set, select its check box.

To search for an option, type search text in the Find box. The list of options is filtered to display only options that contain the search text.

The options you set are saved for each project. For more information on projects, see Working with projects.

Schema Compare for Oracle project options

The project options you can set are described below.

Include deployment script header

Includes a comment header at the top of deployment scripts. The header includes:

  • the date and time the script was created
  • the Schema Compare for Oracle build number used to create the script

Force column order

If deployment requires that additional columns are inserted into the middle of a table, this option forces a rebuild of the table so that column order is preserved following deployment.

A table is rebuilt in four steps:

  1. A new table is created.
  2. Data from the original table is copied into the new table.
  3. The original table is dropped.
  4. The new table is renamed as the original table.

Ignore slow dependencies

Ignores certain dependencies that affect comparison performance when comparing databases. The following dependencies are ignored:

  • type objects in your schema that are referenced by an object in another user's schema
  • REF constraints in your schema that reference, or are referenced by, objects in another user's schema

Note that if this option is not selected, all dependencies will be read, and comparisons may be slow.

Ignore white space

Ignores white space (newlines, tabs, spaces, and so on) in object SQL creation scripts when comparing databases.

Note that white space will not be ignored when the databases are deployed.

Ignore case differences

Ignores case differences in object SQL creation scripts when comparing databases. For example, if you set this option, MYTABLE and mytable are not considered different table names.

Note that case differences in strings and double quoted identifiers are not ignored. Case differences will not be ignored when the databases are deployed.

Ignore double quotes

Ignores double quotation marks around identifiers when comparing databases.

Note that double quotation marks will not be ignored when the databases are deployed.

Ignore comments in PL/SQL blocks

Ignores comments in PL/SQL blocks when comparing databases.

Note that comments will not be ignored when the objects are deployed.

Ignore constraint names

Ignores the names of foreign keys, primary keys, and default, unique, and check constraints when comparing databases.

Note that the constraint names will not be ignored when the databases are deployed.

Ignore storage

Ignores storage properties (physical properties and partitioning clauses) on tables when comparing and deploying databases.

Note that table organization (heap-organized or index-organized) will not be ignored.

Ignore sequence current value

Ignores the current value of sequences when comparing and deploying databases.

If this option is set and you deploy a sequence, the current value of the target sequence is retained. Note that if the current value of the target sequence is not within the MINVALUE and MAXVALUE limits of the source sequence, the current value will be reset to a default value.

If this option is not set and you deploy a sequence, the current value of the source sequence is used as the current value for the target sequence.

Default options

To save your option settings as the default options for all new projects, click Save as My Defaults. To revert to your default settings after making changes, click My Defaults.

To reset all the options to their original settings, click Red Gate Defaults. The Red Gate default options are as follows:

  • Include deployment script header
  • Ignore slow dependencies
  • Ignore white space
  • Ignore case differences
  • Ignore double quotes
  • Ignore comments
  • Ignore constraint names
  • Ignore storage
  • Ignore sequence current value

See also

Working with projects

Was this article helpful?

Search support
Forums