Private Workspaces and Repository Size
Private workspace life
A private workspace gives a user a frozen view of a repository.
When the repository is modified by other dispatched private workspaces, this private workspace keeps the view it had when created.
Since the data corresponding to these views is kept in the repository, its size grows, and may become disproportionate to the actual repository contents.
Private workspace monitoring
More than one user can connect to a single repository via network share. The first time a user connects to the repository, he/she opens a private workspace. This private workspace ends only when the user dispatches, discards, or refreshes his/her modifications, and not when simply disconnecting from the HOPEX repository.
In his/her private workspace, changes made by the user are saved in a temporary space (file for GBMS repository and data for RDBMS repository) dedicated to data of his/her private workspace. The repository is updated only when the user dispatches these changes.
All data accessed by a user is "frozen" for the duration of the private workspace.
Example:
For example, if an object is renamed in the reference repository after the private workspace is opened, the user sees the previous name unless the private workspace is refreshed. However, users connecting after the modification has been dispatched will have a view reflecting the most recent state of the repository.
If other users connected before you dispatch your updates, and are accessing the same data as you, they will have an obsolete view of the data until they refresh their private workspace. Note that when you dispatch your updates, your view is refreshed automatically.
This means that data being accessed by user A and modified at the same time by user B is duplicated. It is stored in its initial state for each user private workspace; if a user makes a change, the previous state is stored along with the new one.
When the updates are dispatched and all users accessing the updated data have refreshed their private workspaces, the previous state is no longer required.
If a user does not want to dispatch his/her private workspace, refreshing it allows the user to avoid a large increase in the HOPEX repository size.
The administrator can set the maximum duration of a private workspace. In that case, at connexion, a message prompts the user to dispatch his/her work or refresh his/her private workspace.
You can audit private workspaces with the HOPEX Administration application.
A private workspace that began before significant modifications were made may cause a considerable increase in repository size, since an image of the previous state of the modified elements is kept until the private workspace is refreshed.The default option when a user disconnects is indicated in the user configuration. It is defined for the entire environment.
The greater the number of private workspaces and the longer their duration, the more the volume of the temporary space (file for GBMS repository and data for RDBMS repository) dedicated to private workspace data will increase. This volume can be reduced by repository backup or deletion, new repository creation or logical backup restoration.
For more information on reorganization of repositories, see "Reorganizing an RDBMS Repository.