Editing Multi-User Geodatabases: An Introduction: Cheryl Cleghorn and Shawn Thorne

Editing Multi-user Geodatabases :
An Introduction
Cheryl Cleghorn and Shawn Thorne
Esri UC 2014 | Technical Workshop |

Assumptions:
 Basic knowledge of relational databases
 Basic knowledge of the Geodatabase data model

File and Personal Geodatabases
Editing Multi-user Geodatabases : An Introduction

Requests:
• Please hold questions until Q&A
• Please silence smart devices

Session Path
• Introduction to the Multi-user Geodatabase

• Versioning
• Multi-user Geodatabase Editing Strategies
• Archiving
• Geodatabase Replication
• Q&A

Session Path
- What is the Geodatabase?
- The Multiuser Geodatabase Management Approach
- Different types of Geodatabases
- The Multiuser Geodatabase
• Versioning
• Archiving
• Q&A

What is the Geodatabase?
• Physical data store
• Core ArcGIS data model
• Transactional model
• COM components

Three Types of Geodatabases
Personal GDB File GDB Multi-user GDB

(3 editions)
Storage format Microsoft Folder of DBMS

Access binary files
Storage capacity 2 GB 1 TB Depends on

per table* edition
Supported O/S Windows Any platform Depends on

platform edition
Number of users Single editor Single editor Multiple editors

Multiple readers Multiple readers & readers
Distributed GDB Check out/check in Check out/check in Replication

functionality One way replication One way replication (all types)
& versioning

Multi-user Geodatabase Data Management Approach
DBMS
Simple classes Short transactions logic

Integrity
Reliability
Flexibility
Scalability
Extend functionality and data integrity

Esri UC 2014 | Technical Workshop | A
Mulit-user Geodatabase Data Management Approach…
Editing and data compilation
Oops!

Multi-user Geodatabase Data Management Approach…
• Versioning workflows
- Long GIS transactions
- Isolation and consistency of long transactions
- Distributed data management
• Robust, customizable framework

WebGIS and the Multi-user Geodatabase
Feature Layer in
Feature Services
Multiuser
Goedatabase

What is a Multi-user Geodatabase?
• DBMS enabled with ESRI’s geospatial technology

• Unique capabilities:
- Many supported DBMSs
- Full, open SQL access
- Versioning
- Archiving
- Replication

Three editions of Multi-user Geodatabase
Scales from small, personal systems up to workgroups and very large enterprises
Desktop Workgroup Enterprise
ArcGIS ArcGIS Desktop and ArcGIS Server Workgroup ArcGIS Server

Product Engine Enterprise
Administration ArcGIS Desktop ArcGIS Desktop ArcGIS Desktop,

(ArcCatalog) (ArcCatalog) Geoprocessing tools

Which Multi-user Geodatabase edition?

Number of Max 3 users, 1 editor at Max 10 clients at one time Unlimited

users any one time No limit to the number of
connections




connections
Supported SQL Server Express SQL Server Express Oracle, SQL Server,
DBMS DB2, Informix,
PostGreSQL




connections
Supported SQL Server Express SQL Server Express Oracle, SQL Server,
DBMS DB2, Informix,
PostGreSQL
Resource Max database size 10 GB Max database size 10 GB No limits

limits 1 GB RAM on a single cpu 1 GB RAM on a single cpu

Session Path
• Introduction to the Multi-user Geodatabases

• Versioning
- What is it?
- Why Use Versioning?

• Archiving
• Q&A

Versioning: What is it?
• Multi-user Technology

Version:
• An alternative view of the Geodatabase
• Edits independent of other versions

Parks
Parks

Why Use Versioning?
• Multiple Editors and Edit Sessions / Workflows
• Different Views of the Geographic Information
• Editing Complex Data (e.g. networks)
• Geodatabase Distribution

Why Use Versioning?...
• Facilitates long edit transactions

• Isolate work across multiple sessions
• Edits do not impact others
• Model what-if scenarios
• Feature Services Workflows

- QA/QC of data collected via feature services
- Isolate crowd-sourced / community reporting information GIS Server
- Information feeds

Session Path

• Versioning
- Versioned Editing
- Non-Versioned Editing
- Editing through SQL
• Archiving
• Q&A

Editing Multi-user Geodatabases
• Short Transactions
- E.g., ATM transactions, Library records, Timecards
Farmland Residential
• Long Transactions
- E.g., Parcel updates
- General geographic editing
• GIS editing utilizes both short and long transactions

Three ways to edit Multi-user Geodatabases
- Versioned Editing (Long Transactions)
- Non-Versioned Editing (Short Transactions)
- Editing through SQL (Short Transactions)

Versioned Editing
• Versioned Edit Sessions

- Through a version
- Concurrent editing
- Long transactions (hours/days)
- Undo/Redo
DEFAULT
Design
Work Order

How Versioning Works
Business or
Base table
• ….Register as Versioned

• Registered as Versioned
- Creates Adds and Deletes tables for tracking edits

• Adding Features
- Record added to the Adds Table
- Version will be referenced (SDE_State_ID Field)

• Deleting Features
- Record added to Deletes Table
- Version will be referenced (Deleted_At field)

• Updating Features
- Record added to both Adds and Deletes table
- Version will be referenced (SDE_State_ID Field)

• Versioned feature classes:

- Base Tables, Adds Tables & Deletes Tables
ArcGIS
Base Tables
Adds Tables
Deletes Tables

Shawn Thorne
Esri UC 2014 | Technical Workshop | Editing Multi-user Geodatabases : An Introduction

Versioned Editing – Reconcile and Post
• How can versions be merged?

Versioned Editing – Reconcile
• Incorporate changes from the target version

Reconcile and Conflicts
• No locks on edit
- Data overwritten?
- Conflict detection
• Conflict Resolution Dialog

Versioned Editing – Post
• Incorporate with target version
- After a post versions are identical

Shawn Thorne

Non-Versioned Editing
• Directly editing the base tables
• Benefits IT integration
Base Tables
Adds Tables
• Database integrity rules
Deletes Tables
• Simple data only (Points, Lines, Polygons)

But I want both…
Base Tables Base Tables

Adds Tables Adds Tables
Deletes Tables Deletes Tables
Versioned Non-versioned

Versioned Editing - Move to Base Option
• Hybrid
- versioned and non-versioned
IT integration
Database constraints
• Simple data only

- Points, lines, polygons, annotation, relationship classes

SQL Editing
• Attributes
• Geometry
- Spatial Types
- Non-ArcGIS Client
- SQL access to geometries
• Versions
• No geodatabase functionality

Multi-user Geodatabase Editing Summary
• Three editing strategies

1. Versioned Editing
2. Non-Versioned Editing
3. SQL Editing
• Which one do I use?

• Depends: > Short vs. Long Transactions?
> non-ArcGIS clients?
> Multi-editor requirement?

Session Path

• Versioning
• Multi-user Goedatabase Editing Strategies
• Archiving
- What is it?
- How is it used?
• Q&A

Geodatabase Archiving: What is it?
• Edit history
- Versioned data
- Non-versioned data
• Temporal queries
Time

Versioned Archiving: How it works
Delta Tables
• Extends versioning Base Table Adds
1. Register as Versioned
Deletes
Default version
2. Enable Archiving F T
Archive Table Editing Multi-user Geodatabases : An Introduction

Versioned Archiving: How it works
• Save edits (or Post) on the Default version

- changes added to archive table
Archive Table
Base Table F T
Delta Tables
Adds
Deletes

Non-versioned Archiving: How it works
Edits
F T
Business Table
Enable
archiving
Current Data View
Business Table
Edits

Geodatabase Archiving: usage
• Two query methods

- specific date and time
- historical marker

Shawn Thorne

Session Path
• Introduction to Multi-user Geodatabases

• Versioning
• Archiving
- Geodatabase Replication
- Q&A

Geodatabase Replication
• Distribute subsets of data Child Child

- Platform independent
Parent
• Data edited independently

- synchronized when needed Child Child

Distributed Geodatabase Use Cases
Central Hub Mobile Users
Feature Services
with Sync
Central Office
Production / Publication
Multiple levels / Replica Tree
Main Office Editors Readers
Other ArcGIS
ArcGIS
ArcIMS
Clients Server
Server
Regional Regional Regional
Office Office Office
Local Local Local Local Local Local Local Local Local Production Publication
Office Office Office Office Office Office Office Office Office Geodatabase Geodatabase

Geodatabase Replication - Concepts
Parent Replica_A
Source
• You can replicate :
- A specific version
- Specific datasets
- A subset of features in the chosen datasets
Child Replica_A
Target
• Transfer updates

Three Types of Replicas
edits
Check out / Parent Child
Check in geodatabase geodatabase
Once only
edits
Parent Child
One-way OR geodatabase
geodatabase
Multiple times
edits
Two-way Parent Child
geodatabase Multiple times geodatabase

Shawn Thorne

Geodatabase Replication - Summary
• Distribute data across Geodatabases
• Different Replication workflows

- Check out / Check in (Personal, File or multi-user geodatabase)
- One-way (Personal, File or multi-user geodatabase – parent is multi-user)
- Two-way (multi-user geodatabases)

Session Path - Summary

• Versioning
• Archiving

Thank you…
• Please fill out the session survey in your mobile app

• Select ‘Editing Multiuser Geodatabases: An Introduction’
in the Mobile App
- Use the Search Feature to quickly find this title
• Click “Technical Workshop Survey”
• Answer a few short questions and enter any comments

Thank you for attending!
Questions??

Editing
Esri UC 2014 | Technical Workshop | Multi-user Geodatabases : An Introduction

Editing Multi-User Geodatabases: An Introduction: Cheryl Cleghorn and Shawn Thorne

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Editing Multi-User Geodatabases: An Introduction: Cheryl Cleghorn and Shawn Thorne

Uploaded by

Copyright:

Available Formats

Editing Multi-user Geodatabases :

Esri UC 2014 | Technical Workshop |

 Basic knowledge of relational databases

 Basic knowledge of the Geodatabase data model

Editing Multi-user Geodatabases : An Introduction

• Please hold questions until Q&A

• Please silence smart devices

Editing Multi-user Geodatabases : An Introduction

• Introduction to the Multi-user Geodatabase

Editing Multi-user Geodatabases : An Introduction

- The Multiuser Geodatabase Management Approach

- Different types of Geodatabases

- The Multiuser Geodatabase

Editing Multi-user Geodatabases : An Introduction

• Physical data store

• Core ArcGIS data model

Editing Multi-user Geodatabases : An Introduction

Personal GDB File GDB Multi-user GDB

Storage format Microsoft Folder of DBMS

Storage capacity 2 GB 1 TB Depends on

Supported O/S Windows Any platform Depends on

Number of users Single editor Single editor Multiple editors

Distributed GDB Check out/check in Check out/check in Replication

Editing Multi-user Geodatabases : An Introduction

Simple classes Short transactions logic

Extend functionality and data integrity

Editing Multi-user Geodatabases : An Introduction

Editing and data compilation

Editing Multi-user Geodatabases : An Introduction

- Isolation and consistency of long transactions

- Distributed data management

• Robust, customizable framework

Editing Multi-user Geodatabases : An Introduction

Editing Multi-user Geodatabases : An Introduction

• DBMS enabled with ESRI’s geospatial technology

- Full, open SQL access

Editing Multi-user Geodatabases : An Introduction

Desktop Workgroup Enterprise

ArcGIS ArcGIS Desktop and ArcGIS Server Workgroup ArcGIS Server

Administration ArcGIS Desktop ArcGIS Desktop ArcGIS Desktop,

Editing Multi-user Geodatabases : An Introduction

Desktop Workgroup Enterprise

ArcGIS ArcGIS Desktop and ArcGIS Server Workgroup ArcGIS Server

Number of Max 3 users, 1 editor at Max 10 clients at one time Unlimited

Administration ArcGIS Desktop ArcGIS Desktop ArcGIS Desktop,

Editing Multi-user Geodatabases : An Introduction

Desktop Workgroup Enterprise

ArcGIS ArcGIS Desktop and ArcGIS Server Workgroup ArcGIS Server

Number of Max 3 users, 1 editor at Max 10 clients at one time Unlimited

Administration ArcGIS Desktop ArcGIS Desktop ArcGIS Desktop,

Editing Multi-user Geodatabases : An Introduction

Desktop Workgroup Enterprise

ArcGIS ArcGIS Desktop and ArcGIS Server Workgroup ArcGIS Server

Number of Max 3 users, 1 editor at Max 10 clients at one time Unlimited

Resource Max database size 10 GB Max database size 10 GB No limits

Editing Multi-user Geodatabases : An Introduction

• Introduction to the Multi-user Geodatabases

- Why Use Versioning?

• Multi-user Geodatabase Editing Strategies

Editing Multi-user Geodatabases : An Introduction

Editing Multi-user Geodatabases : An Introduction

• An alternative view of the Geodatabase

• Edits independent of other versions