Comparing Data

Comparing Data

Select the desired data provider from the drop down list. Some data providers handle a large number of database rows and there may be a noticeable delay as the data is being read.

Let the mouse rest over the selected data provider in the drop down list in order to display hover help describing details about the selected data provider.

The data container will show matching source and target rows in pairs, matching by the extended key.

Extended key fields are colored dark grey (unless there are differences or dependencies).

Differences #

In the simplest case, differences are colored red, as shown in the following example.

config_manager_4.png

The source row has a selection checkbox. It is used to include this difference when generating SQL.

Dependencies #

If a dependency is initially unstatisfied, it will be colored yellow. In the following example, the REF_TO_REF table row #9 refers to the reference data 1001/AOPDED, but this reference data item does not exist in the target schema. The table row #12 refers to 1001/BUS_INT, this dependency is colored red because the target schema already contains this reference data item.

config_manager_5.png

In the above example, there is no selection checkbox on row #9, 10 and 11, due to the unstatisfied dependency.

Double-clicking a yellow-colored dependency will navigate to the referenced item (except for dependencies referring to non-data providers, like Base Company and Reporting Unit dependencies). The following example shows the result of double-clicking on 1001/AOPDED.

config_manager_6.png

The above example shows a number of things:

  • The data provider has changed from ‘Ref-to-ref’ to ‘Reference Data’
  • The back arrow is enabled, it allows easy return to the previous location
  • The list of rows is positioned on the referenced dependency item (row #33)
  • The referenced dependency item has a selection checkbox
  • The referenced dependency item is colored cyan, to indicate that this item is referred to by one or more dependencies that were intially unsatisfied. A cyan-colored item is also called a reverse dependency.

If one now selects the checkbox and clicks the back arrow, the result will be as follows.

config_manager_7.png

The rows #9, 10 and 11 now have a selection checkbox, because the referenced item 1001/AOPDED was selected and will result in an INSERT on the target schema.

The above examples showed an INSERT case (target rows missing), where the item having a reverse dependency must be selected before the items having a dependency can be selected. In the DELETE case (source rows missing), the order is opposite: The items having a dependency must be selected before the item having a reverse dependency can be selected.

External Dependencies #

External (non-data provider) dependencies, like Base Company and Reporting Unit dependencies, are shown with a olive color. It is not possible to navigate to the referenced value by double-clicking an olive-colored cell.

config_manager_8.png

Notes #

Some data providers / database tables contain a link to a note. Typically, the link is a Foreign Key, like FK_NOTE, pointing to the CNU_NOTE table. This means there is a dependency also on the CNU_NOTE and BIG_STRING_SUB tables. In order to simplify this, data providers containing note references will create a “virtual” column for the note string. When there is a difference in the note string, and SQL is to be generated, the data provider will create the necessary SQL for CNU_NOTE and BIG_STRING_SUB.

In other cases, the data provider has a Foreign Key column which points to the BIG_STRING table. This a kind of “note”, which will be handled with a “virtual” long description string column as described in the preceding paragraph.