About Merging Databases
You use the Merge tool to merge selected standard databases into one new standard database that you name.
For each type of database record, merge rules and selection order determine the contents of the new database. The merge process merges databases table by table, formatting columns as necessary. Unique records are added to the new database, while duplicate records are ignored. This may mean that some records are renamed or renumbered in the new database.
To merge databases successfully, the following settings must be the same for each source database.
| Setting | Description |
|---|---|
| Registration name |
You can merge databases only if the publisher of the source database:
If any of the source databases is Sage-protected (for example, Means, CK, RK, or EK), the new database uses "Sage" as the publisher. Otherwise, the publisher for the new database will be your current registration name, or blank. You can enter a publisher for the new database in the Standard Database pane, later. |
| Size of phase suffix |
You cannot change the phase suffix. However, you can view the phase suffix in the Standard Database window in the Estimating Management Console or in the Standard Database Settings window in the Estimating application. |
| Job cost system name |
You can edit the Job cost system name in the Standard Database window. |
| Default job cost categories |
You can edit the default job cost categories in the Standard Database window. (After selecting the Job Cost system name, click the [] button.) |
| Default crew pricing method |
You can edit the default crew pricing method in the Standard Database window. |
Generally, if subsequent databases contain duplicates, the new database will use the values from the first database in the list of databases you select for merging. In some cases, group records (such as group assemblies, crews, and rate tables) in the merged database can appear to be sorted incorrectly because of the renumbering method used during the merge. Where there is a conflict between a group record and a non-group record, the non-group record is used in the merged database, and the group record is renumbered.