Versioning scenarios
Release 9.1 Last modified April 26, 2005	Print all topics in : "Working with a versioned geodatabase"

NOTE: Versions cannot be created or edited in ArcView.

The following scenarios show how an organization can implement its work flow process using a versioned database. These examples demonstrate several techniques available for performing long transactions in a multiuser environment. It is likely that organizations will, in some manner, use each of these techniques, depending on the task.

Scenario 1: Simple database modifications

Task:

Multiple users are concurrently editing the database, performing common map sheet changes, such as inserting new features, updating attributes, and removing out-of-date facilities.

Solution:

Users can connect to the DEFAULT version (simultaneously), start editing, and save their changes when their work is complete. Users do not have to create new versions to modify the database. If another user has edited the DEFAULT version since the current user started editing, the user saving is notified that the version has been changed, and, therefore the version will need to be saved again. Users may bypass this warning message by enabling autoreconciliation in the ArcMap Options dialog box. Also, if two users modify the same feature during their edit sessions, the second user to save encounters a conflict. The user then has to decide what the feature's correct representation is and save the edit session.

Scenario 2: Transactions spanning multiple days

Task:

Update the database to incorporate new and updated facilities in the field, which will likely require multiple edit sessions and a couple of days to complete.

Solution:

A user creates and switches to a new version derived from the DEFAULT version. The user starts editing the new version and begins modifying features and saving as required. The user can resume the edit session, as appropriate, the following day or possibly the following week. When the changes are complete and ready to be posted to the DEFAULT version, the user must first click the Reconcile button on the Versioning toolbar. If conflicts are detected, the user can resolve the differences and complete the transaction by clicking the Post button. The posting process applies all the changes in the user's version to the DEFAULT version. The user can then delete the version.

Scenario 3: A work flow process

Task:

Create individual versions for each step or stage of the work order and work flow process and post the work order to the database.

Solution:

A user or supervisor creates a new version derived from the DEFAULT version. The user starts editing the new version and begins modifying features or creating a new design. When the user has completed the design or proposed modifications, the work order can be submitted to a supervisor for review. At this time, a new version can be created to ensure the preservation of the initial design. The new version can then be further modified or adjusted as required. Once the work order has been approved for construction, another version can be created. The purpose of this version is to reflect any changes that may occur while the work order is being constructed in the field. Finally, as the construction is completed and the new facilities are in service, the work order must be posted to the database. A user can then start editing the work order, perform a reconcile with the DEFAULT version, resolve any conflicts if necessary, and post.

The solution allows the organization to create new versions of the work order for each step of the project—initial design or proposed version, a working or accepted version, and a version for the construction phase. Each version is preserved and available to look back on for historical purposes. The final step is to post the constructed version to the database. The project completes a full circle from start to finish, creating individual versions at each step.

Scenario 4: Restricting permissions to the database

Task:

The organization's supervisor has restricted write access to the DEFAULT version, requiring managerial review of each user's edits prior to posting the changes to the database.

Solution:

To restrict write permissions to the database (the DEFAULT version), the SDE administrative user can set the permission of the DEFAULT version to protected using the version manager. This allows users to continue to view the DEFAULT version but does not allow users to start editing the version. Therefore, users will need to create new versions for editing the database, similar to Scenario 2. When a user has completed and saved the edit session, the SDE administrator can reconcile the version with the DEFAULT version. To accomplish this task, the manager who connects to the database as the SDE administrator starts editing the user's version and clicks the Reconcile button. The process will merge all the changes in the user's version and the DEFAULT version. If conflicts are detected, the manager can resolve the conflicts and save the edit session. Once the edits are acceptable to the manager, the version is ready to be posted to the DEFAULT version. The SDE administrative user can then start editing the version, perform a reconcile, and post the version. The user's version can then be deleted.

Scenario 5: Compressing the database

Task:

The geodatabase has been edited for an extended time, and the number of database states and rows in each feature class's delta tables has significantly increased. How can you improve performance by running the Compress command?

Solution:

The Compress command will remove all database states that are no longer referenced by a version and move all the rows in the delta tables, which are common to all versions, to the base table. To achieve the maximum benefit when running the Compress command, you can optionally first reconcile, post, and delete each version with the DEFAULT version. Sometimes this may not be a reasonable option based on your organization's work flow. At a minimum, to improve performance, simply reconcile each version with the DEFAULT version and save, then perform the compress. This will ensure that all the edits in the DEFAULT version will be compressed from the delta tables to the business table. Remember, the Compress command can still be executed without first reconciling, posting, and deleting each version, but the benefits may not be as noticeable.

Please visit the Feedback page to comment or give suggestions on ArcGIS Desktop Help.
Copyright © Environmental Systems Research Institute, Inc.