Diff Profile Editor Tab

Opened from: Home tab
Applicable tab-specific toolbar actions: None
Applicable object types: tables and views

This tab allows to setup diff profile settings:

Tab shows diff profile file name in the header and has three collapsible sections: Table mappings, Queries and Data slices.

Table mappings section shows a list of saved custom data diff mappings. This list has the following columns and actions:

Data - name of the table, view or 'table vs other table' kind of title. Represents a hyperlink which opens a Data diff tab with the data of the given table/view using mappings saved in the diff profile
Column mapping (keys / total columns) - shows the number of saved column mappings. Displayed as 'N key(s)' for the view key mappings saved using Query key columns dialog, or as 'key count / total column count' for mappings saved from Custom data diff dialog. Represents a hyperlink opening corresponding mapping dialog
Show in Batch data diff - Yes/No toggle allowing to show this custom mapping in the Batch data diff tab
Created - the time when this mapping was created. It may happen that mapping was created before the application has started to track the mapping creation date, in this case this timestamp can be shown as '0001-01-01:00:00:00'.
Delete - remove these mappings from the diff profile.

Queries section shows a list of queries saved using Query result diff tab. This list has the following columns and actions:

Title of the query, this value is specified when the query is added to the diff profile.
Query text - text of the query. In the case of the 'Split query' option this text shows only one of the queries (but both queries are stored in the diff profile). Represents a hyperlink opening Query result diff tab with that query. Diff profile query text is updated on each query run
Show in Batch data diff - Yes/No toggle allowing to show this custom query in the Batch data diff tab
Created - the time when this query was created. It may happen that query was created before the application has started to track the query creation date, in this case this timestamp can be shown as '0001-01-01:00:00:00'.
Delete - remove this query from the diff profile.

Data slices section shows a list of saved data slices. New data slices can be created in the Batch data diff tab. This list has the following columns and actions:

Name - name of the data slice. Represents a hyperlink opening this data slice, it opens a Batch data diff tab in the 'Data slice' mode
Item count - the number of objects (tables, views, etc.) in the data slice
Created - the time when this data slice was created
Delete - remove this data slice from the diff profile.

Custom schema/name mapping rules allow to set up custom rules to match schemas and normalize object names across different naming conventions. For example, to remove delimiter chars from name, setup schema mapping, and provide automatic table match like prod.sale_preson vs Product.SalesPerson.

☐ Use custom rules [Save changes] [Discard changes]
Db1 / Schema1 / Name1 refer to the database opened in the left panel.
Db2 / Schema2 / Name2 refer to the database opened in the right panel.

Schemas processing allows to setup schema mapping and extract part of object name in schema-less DBMS that can be mapped to a schema in schema-based DBMS. For example, for MySQL table prod_salesperson we can extract "prod_" as a scheme and then using prod_ vs Production mapping map automatically prod_salesperson to Product.SalesPerson in SQL Server.

☐ Match objects by schema and name (overwrites related Schema Diff setting)

Extract schema from table name prefix in schema-less DB to match schema-based DB (comma-separated list):
(prefix list)

Schema mappings:
(schema mappings table, columns: Schema1, Schema2)

Names processing allows to setup name normalization rules to automatically match objects between databases using different object naming conventions:

Normalize object names to match across different naming conventions (e.g., tblUserLocations vs user_location).
For special cases not covered by normalization, use Explicit object mappings (see below).

☐ Use same normalization for both databases

☐ Normalization for Db1: (rules table) ☐ Normalization for Db2: (rules table)

Each rules table has columns Trim At (dropdown of Start, End and Everywhere), Value, and Max Count (for Everywhere). Max Count is ignored for Start and End, and it is optional for Everywhere. Rules are applied in the same order as they are listed. For example, for the object name "prod_sales_person":

Trim at start "prod_" then everywhere "_": result is "salesperson"
Trim everywhere "_" then at start "prod_": result is "prodsalesperson"

Explicit object mappings are the top-priority rules to handle special cases that can't be covered by general rules:

These mappings override the schema and name handling rules specified above. Use it for special cases which can't be covered by general rules.
Specify both schema and name for schema-based DB and name only for schema-less DB.

(schema mappings table, columns: Schema1, Name1, Schema2, Name2)

Free Version Limitations

The whole tab is not available

Last updated: 2025-10-09