Versions Compared

Key

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

In most cases the default mapping mechanism that pairs the objects based on the schema name selected schemas and the object name is what is needed. However, there are often scenarios in which the same table may be owned by different schemas in different databases, or the tables on the development server for example may have the names prefixed with dev_ whereas the same tables in the production server do not have that prefix. In such cases you may want to define certain mapping rules that would allow you to pair objects that would otherwise not be paired together by IDERA Idera Data Compare for Oracle Database.

The Mapping Rules can be accessed from the ribbon or from the action links on the right panel of the comparison tab.

There are three types of rules you can set:

...

. By default

...

data compare performs an exact match

...

on

...

the object names. However, you can choose to ignore certain prefix

...

or postfix. For example

...

, if you ignore the "dev_" prefix on the left schema and the

...

"prod_" prefix on the right schema, a table named dev_employees on the left schema will be mapped to a table named prod_employees on the right schema.

Image Added


Excerpt

Total compare from data to schema with IDERA Comparison Toolset. Learn more > >

...