Global Merging on Non-Extract Databases

Take care when merging project databases. Databases can only be merged at their primary locations. It is important to note that when a project database is merged, the database session will effectively be lost. Thus the ability for Global to send only session changes is lost too.

It is therefore recommended to use the Global Merge command (syntax REMOTE MERGE (or select Remote > Global Change Management > Global Merge Changes from the ADMIN menu bar) to synchronize and merge the database at all secondary locations (unless the database is non-propagating). This prevents propagation of the entire database on the next update.

If there are any users in a database at its primary location, the database cannot be merged.

The Global Merge merges the database at secondary locations after it has been merged at the primary location in order to prevent unnecessary copying of the entire database when it is next updated.

The user is advised to stop scheduled updates and avoid adhoc updates when using Global Merge. If scheduled updates are left in place, then unnecessary copying of entire databases will be undertaken. There is also a danger of reverse propagation from secondary to primary location, with the result that changes made by users at the primary location would be lost.

Note:
Database extracts which own other extracts cannot be merged using REMOTE MERGE. Refer to Merging Extract Databases for further information.