Merge Sessions

The AVEVA base product sessions enable a history of changes to the database to be recorded. When a new session is made, the changed data is appended to the end of the database file. Appending updated data to files will increase the disk space required. If the history information is not required, and to save disk space, the user can compact a database by merging sessions. You can specify that the changes up to or after a given date, session number or Stamp will be merged.

For example, there may be a session which corresponds to a project milestone which the user needs to keep, in which case they can merge the sessions around this. In other cases the user may want to merge all sessions up to a given date, within a given week or after a specific Stamp. Merging the database sessions has no effect on any database references into that database from other databases.

To merge sessions, click Merge on the Manage tab. The Merge Changes window is displayed.

You can merge the changes to All Project Databases, the System databases, or the Single database selected above.

If the user chooses All Project databases, they can merge all changes, or changes up to or after a given time, date, session number or stamp.

If the user chooses System database, they can merge changes up to or after a given time, date, session number or Stamp.

If the user chooses Single database, choose a database from the Available databases list. Clicking Database Sessions will display the Database Sessions window, which lists information about the existing sessions for the database.

Rebuild list is used to update the list of databases. For example, if a new database has been created while the window is displayed, the list will not be updated until the window is closed and re-displayed, or click Rebuild list.

(Refer to Merging Changes for Extracts for information about merging sessions in extracts.)

If the External Drawing Files (sdb, pic) check box is ticked, files that become obsolete because of the merge will be deleted. Currently this options is valid for PADD databases only and considers .sdb and .pic files.

After specifying the sessions to merge, click Apply to merge changes. Some session data will be deleted. The sessions remaining are those that the user has either kept deliberately, or stamped sessions, as these are considered permanent and are not merged.

If an AVEVA Engineering session is merged, drawing revisions are not merged. The drawing revision data is not deleted.