This dialog is opened to confirm and customize batch data merge/delete action from the Batch data diff tab:
The dialog contains the following sections.
You're going to {merge or delete} data for selected tables.The next warning is shown only if we are going to process tables with changed column definitions:
Target database: {Database display name}
Some of selected tables have 'Changed columns'=Yes, this means that:The next warning 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.
Data merge and deletion does not make any backup, please make sure that you've done it yourself if needed.
Please specify which rows should be {merged to or deleted in} the target database:
○ New ○ Changed ○ New and changed
If we are performing a merge (not deletion), then we may have additional options for script generation.
New and 'New and Changed' options provide an additional option for AutoNumber column values:
Some of selected tables have AutoNumber primary keys. If the following option is disabled, DB engine will generate new values which most likely will be different
☐ Import existing AutoNumber values for new rows
In the case of merge with a 'New and Changed' filter, the dialog also suggests to delete new rows in the target database 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
Wrap table data operations in a transaction on the target database, with rollback on any first failure.If enabled, application calls BeginTrans() DAO call before rows processing, and CommitTrans() in the end of successful execution. If any row fails, then execution is stopped and Rollback() call made.
Can also provide better performance.
☐ With transaction
This section is shown if the target table(s) has data macros with related events. For the Merge it is AfterInsert or AfterUpdate events, and for Delete it is AfterDelete events:
The target table has data macros which may modify data in other tables (application does not analyze their logic). To ensure that only the target table is affected, you can temporarily remove data macros.
The option itself and additional comment regarding its behaviour:
☐ Temporarily remove data macros
Data macros disable is performed out of transaction.
If the option is enabled, application removes data macros and then creates them back during the merge/detele operation.
