This dialog is opened to confirm and customize batch data merge/delete action from the Batch data diff tab:
The dialog contains the following explanatory text and configuration options:
Data merge and deletion does not make any backup, please make sure that you've done it yourself if needed.The next section is shown only if we are going to process tables with changed column definitions:
Some of selected tables have 'Changed columns'=Yes, this means that:The next section is displayed if there are any tables that cannot be merged due to missing or changed key definitions:
- source table may have columns that are not going to be merged,
- some column data types can be changed, data can be truncated or not merged at all.
Your selection also contains one or more views or tables without common key - they are not going to be processed.
The next section displays the target database and asks for a desired new/changed rows filter to apply:
Target database: {Database display name}
Please specify which rows should be {merged or deleted} to the target database:
with mutually exclusive options to process New, Changed, or New and changed rows.
In the case of merge with a 'New and Changed' filter, the dialog also suggests to perform deletion of rows missing in the source to ensure that the target rows match the source rows exactly:
It seems that you want to merge all changes to the target db. By default this option inserts missing rows and updates changed rows. However the target table may contain rows which are missing in the source and this will keep the set of rows different even after completion of merge. You can eliminate these changes in two ways: 1) after completion of Merge action run Delete action on the target db, or 2) select the option below:
☐ Delete new rows in the target database
