Data Merge Warning Dialog

This dialog can be displayed to request parameters for the upcoming data merge/delete script generation. The dialog is triggered by the Merge or Delete actions in the Data diff tab.

for SQLite, data merge warning dialog

The Free version excludes some options and just warns about potential limitations instead:

for SQLite, data merge warning dialog (free version)

Once the confirmation is OK, the next step is typically script generation and the Execute script dialog (see below for exclusions related to Id-Remap and 'Update changed only' scenarios).

The dialog contains the following sections.

Action

This section is always displayed.

You're going to {merge or delete} one or more rows
Target database:
{Database display name}
Click OK to proceed with script generation using the settings below. This action can be canceled on the next step.

Id-Remap Merge

This section is shown only for the merge action in the Standard version when it relates to the Id-Remap Merge scenario:

This table has AUTOINCREMENT primary key and the database contains other tables referencing these primary key values by foreign keys.
- if we merge the source primary key value as is into the target, then in the target this value can be already used by some other entity and its data will be overwritten,
- if we merge the source foreign key value as is into the target, then this row can be bound to the wrong entity.

Target database will generate new values for these primary keys and we'll create additional mapping tables to keep mapping between source and target id values. When we merge the foreign key values, we'll replace them with newly inserted parent id values using these mapping tables. After operation completion mapping tables can be used to check and troubleshoot the merge result and to rollback/remove this data without need to restore backup.
In case of Id-Remap Merge, all the processed rows are going to be INSERTed into the target, no UPDATEs or DELETEs. The New/Changed rows filter below specify only which rows to take from source, but not how they are going to be processed in the target.

If Id-Remap Merge can be applied, this text is followed by the option to enable it:

☐ Use Id-Remap Merge

In this case, the next step in our merge execution flow will be the Id-Remap Merge dialog to set up additional configuration for Id-Remap Merge.
Otherwise (partucularly, if current table or its all children have no dependency level), the dialog will display an explanation of why it cannot be applied:

Id-Remap Merge can not be used because this table has no dependency level. Click OK to proceed merge with the regular data merge.

You can find more information about table dependency levels on the appropriate help page, and more information about why it is necessary for Id-Remap in the Id-Remap Merge dialog help page.

Auto-generated primary key values

This section is shown under the following conditions:
- this table has AUTOINCREMENT primary key,
- it is a merge action (not delete),
- Data diff tab from where the dialog is called has filter that can include new rows (show all, or new, or new and changed)
Section content:

If disabled, DB engine will generate new values which most likely will be different
☐ Import existing AUTOINCREMENT values on INSERT

Merge all pages

This section is shown when you select all rows in the data diff and want to perform a batch merge or delete action on them, provided that the table has more rows on other pages. The Standard version asks if you want to process all pages:

You've selected all rows on the current data page, but there are more rows on other pages.
Do you want to process all rows from all pages?
☐ Process all pages

The Free version simply warns that only the current page will be processed:

You've selected all rows on the current data page, but there are more rows on other pages which are not going to be processed.

Update only changed

This section is shown only for the merge (not delete) action in the Standard version and when the expected script items may include UPDATE statements. As a result, this section is not displayed when the Data diff tab had a filter to show only new rows.

If the generated script will contain UPDATE statements, it can include all or only changed column values. In the last case, script will not be generated for unchanged rows.

As mentioned above, this option excludes unchanged rows from the generated script. If it turns out that all selected rows are unchanged, then the merge action concludes with a No changes to merge message.

Transactions

This section is always displayed.

Wrap table data operations in a transaction. Can also provide better performance.
☐ With transaction

If enabled, the generated script is wrapped with BEGIN TRANSACTION and COMMIT statements.

Default values

The default state of Auto-generated primary key values, Merge all pages, Update only changed, and Transactions options is taken from previous confirmation.

Free Version Limitations

Update only changed and Id-Remap Merge sections are not available.
Merge all pages is just a notification.

Last updated: 2025-06-06