AVEVA Global User Guide
Local Administration
: Merging Changes in a Global Project
Merging Changes in a Global Project
Databases can only be merged at their primary locations.
Note:
When a project database is merged, the database sessions will be lost. Thus the ability for Global to send only session changes is lost too.
It is therefore recommended that you remotely merge a project database, as this also synchronises and merges the database at all secondary locations automatically (unless the database is non-propagating). This prevents propagation of the entire database on the next update. To remotely merge a database, refer to
Global Change Management
for further information.
Database merges should be executed at times when users are not accessing the database. It is also recommended that there should be no users at secondary locations, since the merged database cannot be received until these users have left the database.
1974 to current year.
AVEVA Solutions Limited and its subsidiaries. All rights reserved.