The SDB Merge tool is used to connect two SDB databases and display the differences in data between the two databases on the user interface. Using this visual representation the users can choose the data to merge. Merging of data is always from the source to the target database.
Ability to compare Non-CMS and CMS data separately
When a user logs in to the SDB Merge tool, the following modes are available:
Differences not shown in hierarchy
Show differences in hierarchy
This release of SDB Merge Tool provides the ability to compare Non-CMS and CMS data separately. When you select Show differences in hierarchy, it compares the Non-CMS data and the CMS data separately. This granular approach would provide the flexibility to run the comparison of the Non-CMS and CMS data together or separately.
Recommendation: For efficient use, it is recommended to compare the Non-CMS data and CMS data in two separate steps. For instance, initiate the comparison of the Non-CMS data and then compare the CMS data.
A node is skipped if it is observed that the data comparison of that node takes more than the expected run time. All the records of the skipped nodes are displayed in the log file with Node skipped for comparison because time taken to retrieve data from database exceeds Timeout for DB Comparison note highlighted in Red. You can compare such nodes in the user interface later.
Ability to add Smart Materials data into an existing customer database
The Standard Database now enables you to add all the sample data related to Smart Materials workflows data, which includes E&PI (BOM), E&PI (Requisition), MSCM, and Site modules, to the existing SDB instances. You can do this by using migrate or copy functionality of the SDB Merge Tool.