Skip to content

Compare Metadata

One may compare two different models, configurations or glossaries or two versions of the same model using the comparator facility.

Steps

  1. Sign in as a user with at least the Metadata Viewing capability object role assignment on the semantic mapping.

  2. Either:

    • Navigate to the object page for the object you wish to compare with and select More actions... > Compare with

    • Go to Go to MANAGE > Repository and either:

      • and right click any model, configuration or glossary in the Repository Panel, and select Compare with....

      • Or one may select a version of a model in the Repository Panel where you want the model to be located, and select Compare with Previous...

  3. You are presented with the Compare utility panel.

  4. From here you may:

    • Drag and drop any other matching model, configuration or glossary into the Target or Source.

    • Swap the Target and Source

    • Specify the option for the comparison, including

      • Match Type

      • Objects to Detect

      • Additional Compare options

      • Case Sensitive comparison

      • Specific Comparison Scope

    • Expand ( ) or Contract ( ) objects in the tree

    • Download ( ) the results as a CSV file

    • Filter ( ) the results

    • Match objects

    • Switch to Merge if comparing two versions of a Physical Data Model.

Compare Data Store Model Versions

In this example, we will compare two single-model data source models. There are several versions of the DDL for the models in the models folder.

Example

Create a new model. Complete the dialog as follows:

In the Import Setup tab specify in the File parameter the location:

C:\temp\Models\MetadataManagement\Finance_ConfigurationVersions\v1\DatabaseDDL\FinanceDWStaging.sql

And "dbo" as the Default schema.

Click SAVE and then IMPORT. Click IMPORT again without checking any boxes.

When the import has completed, in the Import Setup tab update in the File parameter with the location:

C:\temp\Models\MetadataManagement\Finance_ConfigurationVersions\vComplete\DatabaseDDL\FinanceDWStaging.sql

And again click Save and then IMPORT. Click IMPORT again without checking any boxes.

Go to the Versions tab.

There are now two different versions of this model in the repository. The latest one is in the current configuration.

Click OPEN and select More actions... > Compare with previous version.

Click the row for the PaymentAmount column with the difference icon .

The difference is in the Length of the data type.

Scroll down to the bottom of the comparison.

We see three table (AccountCategory, Category and CategoryGroup) have been added with the latest version.

Click the Filter icon to show only New Objects.

Click Show Statistics:

Click SWAP to change the order of the comparison:

The three tables are now New Objects, rather than Missing Objects.

Click COMPARE OPTIONS.

One may control the different options of the comparison.

Match Objects

In many cases there are expected differences between models, e.g., a difference in schema name, that one wishes to ignore and continue the comparison as if the actually matched (had the same name). You may use the Match option to inform the comparator that they should be treated as equivalent and thus perform the comparison on the contained objects (e.g., tables in the schema).

Example

Navigate to the object page for the Adjustments model.

Choose Compare with previous version from the More Options... menu.

Note, there are two Catalog level objects with names based upon the year they were valid for. Unfortunately, this difference in name means that the comparison reports that these are two separate objects and does not try to compare their contained objects. You may select both rows (Adjustments2025.sql and Adjustments2024.sql) and the right-click and select the Match option to inform the comparator that they should be treated as equivalent and thus perform the comparison on the contained objects (e.g., tables in the schema).

The result is the comparison now includes the objects inside the two catalogs:

Compare Multi-Model Versions

In this example, we will compare two multi-model data source models. In this case, the model will have a directory structure and the comparison will be performed at two levels (the directory structure and at individual leaves that are internal models).

We will use the data lake as the multi-model. However, there are no additional versions of the data lake in the models folder, so we will edit one of the files.

Example

Create a new model. Complete the dialog as follows:

In the Import Setup tab specify in the File parameter the location:

C:\DataCataloging

Click Save and then IMPORT.

When the import has completed, we will now make some changes for the comparison.

C:\DataCataloging\AdventureWorks Data Lake\HumanRessources

And rename Department.csv to be Dept.csv.

Edit Shift.csv and do the following:

  • Change the data values for the first column (ShiftID) to "S1", "S2" and "S3"

  • Rename Name to ShiftName

  • Add a column Hours at the end of all the lines in the file.

The result should be like this:

Now, again click IMPORT on the model to import a new version.

Be sure to check the Full source import instead of incremental checkbox in order to avoid incremental harvesting.

Go to the Versions tab.

There are now two different versions of this model in the repository. The latest one is in the current configuration.

Click OPEN and select More actions... > Compare with previous version.

Click the row for the Shift.csv column with the difference icon .

The differences are in the model representing the Shift.csv file.

Click COMPARE MODELS.

Click the row for ShiftID.

The data type changed, as we did in the file earlier.

We see also Name was added and ShiftName removed. The comparison direction is critical to the presentation and determines whether something is considered added or removed.

Click SWAP.

Now, we see the added and removed icons in a more appropriate order, where we added the Hours column as well as renaming Name to ShiftName.

Comparing Different Models

In this example, we will compare two different model versions, rather than versions of the same model. Obviously, unless the models are relatively similar, the report will not be that effective.

Example

Navigate to the model and select More actions... > Compare with previous version.

Use the Select a source Version navigation to pick the Staging DW model.

Comparing Data Mapping

In this example, we will compare two instances of a data mapping, rather than imported models.

Example

This one data mapping model contains several query mappings inside and we will compare all of them.

Go to go to More Actions in the upper right and select Export

Go to the Data Lake on S3 to Staging data mapping model

and select Compare with previous version.

A screenshot of a computer Description automatically
generated

A screenshot of a computer Description automatically
generated

Comparing Configurations

In this example, we will compare two different configuration versions, rather than models.

Example

Go to MANAGE > Repository, expand the Demo Enterprise Architecture configuration, right-click the Development version, and select Compare with previous version.

A screenshot of a computer Description automatically
generated

A screenshot of a computer Description automatically
generated

Was this page helpful?