Esri UK Store

Main Services Learning Credit FAQs Certification

Implementing Versioned Workflows in a Multiuser Geodatabase

Call for Price

A successful multiuser editing environment requires a sound versioning workflow that minimises disruption to editors, ensures the integrity of GIS data, and integrates well with existing business workflows—all while maintaining optimal database performance. This course explores a variety of versioned editing workflows and examines how versioning decisions impact data accuracy and database performance.

3 Days
Who is this course for?
GIS Technical Leads
GIS Database Designers
Database Administrators
Deploy a versioning workflow that meets your organisation’s needs.
Efficiently load data into a versioned feature class.
Manage multiple geodatabase versions.
Monitor and maintain database performance in a versioned editing environment.

ArcGIS 2 – Essentials of ArcGIS 10.x for Desktop and or equivalent knowledge is required.

Choosing a multiuser editing environment
Registering data
ArcSDE administrator and data owner responsibilities

Organising versions
Version tree
Creating and deleting versions
Version properties
SDE_Versions system table

Editing non versioned data
Preparing ArcMap for nonversioned editing
Impact of concurrent edits by multiple users

Delta tables
Registering and unregistering data as versioned
How edits are stored

Managing versioning system tables
Overview of system tables
How system tables store feature edits
Maintaining database performance

Merging state lineages
Implicit reconcile and post operations
Explicit reconcile and post operations
Version and feature class permissions

Reviewing conflicts
Defining conflicts
Conflict resolution options
Topology edit conflicts
Viewing version differences

Bulk-loading data into versions
Simple Data Loader
Object Data Loader
Improving performance after a bulk load

Compressing a versioned geodatabase
Performing a full compress operation
Reviewing the Compress log

Registering data as versioned with move-to-base option
Why use the move-to-base option?
Best practices for handling conflicts
Undetected conflicts

Versioned editing with non-Esri applications
Creating versioned views
Querying and editing versioned feature classes using versioned views

You may also like…