Exercise 8: Load data, register it as versioned, and create a version

Available with Standard or Advanced license.

Complexity:

Beginner

Data Requirement:

ArcGIS Tutorial Data for Desktop

Goal:

Log in as a geodatabase administrator and import a shapefile. Register a feature class as versioned, create a geodatabase version for editing, and assign permissions for the version.

In Exercise 4, you granted manager1 administrator permissions to the buildings08 geodatabase. This allows manager1 to write to the geodatabase and perform certain administrative tasks. You will perform a few of these administrative tasks in Exercise 10.

In this exercise, you will connect as manager1, import data, register the new data as versioned, and create a public version that editor1 can use to edit the data.

Note:

Only the owner of a dataset can register it as versioned.

Log in as a geodatabase administrator

Log out of the computer and log back in as manager1.

1. Log in to the computer as manager1.

   On most Windows operating systems, you can use switch users to log in as manager1.

2. Start ArcMap, open the Catalog window, and expand the Database Servers folder in the Catalog tree.
3. You must add the database server because manager1 has not added it yet. For instructions on how to do this, refer to the "Adding a database server" section of Exercise 1.

Import data as manager1

Import the railroads shapefile to the Osokopf geodatabase.

1. Connect to the database server in the Catalog window.
2. Right-click the Osokopf geodatabase, point to Import, and click Feature Class (single).
3. Click the browse button to navigate to the data.

   The Input Features dialog box opens.

Since this is the first time manager1 has connected to the database servers tutorial data, you must add a folder connection.
4. Click the Connect To Folder button on the Input Features dialog box.

   The Connect to Folder dialog box opens.

5. Navigate to the DatabaseServers tutorial directory and click OK to add the folder connection.
6. Choose railroads.shp and click Add.
7. Type railroads in the Output Feature Class text box of the Feature Class To Feature Class tool.
8. Click OK.

The Osokopf geodatabase now contains two feature datasets owned by the dbo user: one feature class owned by editor1 and one feature class owned by manager1.

Register the new feature class as versioned

The changes that will be made to the railroads feature class could take the editor a while to complete. For that reason, you will register the feature class as versioned so the editor can perform versioned edits. Versioned editing allows a user to edit a feature class in isolation from the production version of the feature class and, therefore, does not block the feature class from being accessed by other users.

1. Right-click the railroads feature class in the Osokopf geodatabase, point to Manage, and click Register As Versioned.

   The Register As Versioned dialog box opens.

2. Leave the Register the selected objects with the option to move edits to base option unchecked and click OK.

Dive-in:

When you register a feature class as versioned, two system tables are added to the geodatabase to track edits that are made to the versioned feature class.

Create a version

When performing versioned edits, you could edit the Default version of the geodatabase. However, for the purposes of this tutorial, you will create a separate version in which editor1 can perform edits.

Tip:

For an explanation on geodatabase versions and versioned editing, see A quick tour of versioning and its related topics.

1. Right-click the Osokopf geodatabase, point to Administration, and click Administer Geodatabase.

   This opens the Geodatabase Administration dialog box.

2. Click the Versions tab.
3. Be sure the Transactional or Tree View tab is active.
Currently, only the Default version is present. You will create a version from the Default version.
4. Right-click the Default version and click New Version.
5. Type railroadv1 in the Name text box.
6. Type a description for the version.
7. Click Public from the Access list.

   This allows editor1 to edit this version. If you instead chose Protected, editor1 could see the version but not edit it. If you chose Private, editor1 would not even be able to access the version.

8. Click OK to close the New Version dialog box.

   There are now two versions showing on the Versions tab.

9. Close the Geodatabase Administration dialog box.

You logged in as manager1, imported data, registered it as versioned, and created a geodatabase version. In Exercise 9, you will connect as editor1 to the new geodatabase version, edit the data, and reconcile and post your changes to the Default version.

Feedback on this topic?