Slide 1

Slide 2

Slide 3

Workflow that manages concurrent multiuser editors on a single ArcSDE data source Versions represent states or views of the geodatabase Edits are maintained in delta tables until compression

Slide 4

Before: Have single editor in each file geodatabase Notify editors when to disconnect from database Copy edits from the file geodatabases to a staging file geodatabase, then push those to SDE Repeat process for each database After: Multiple editors in same source Run maintenance when all users disconnected

Slide 5

Eliminating dataset duplicates Faster processing times for dataset edits Version control Collaboration

Slide 6

Slide 7

Register data as versioned Create versions and grant privileges Provide training to editors

Slide 8

Default QAQC Named Version

Slide 9

Default Named Version Default User Edit Default Directly 2-Level

Slide 10

Slide 11

Slide 12

Reconcile edits before beginning an edit session Database administration Everyone has to be out of database in order to perform full compression Checking the process_information table was cumbersome (fixed in 10.1) Need elevated permissions to disconnect users

Slide 13

Resolving conflicts Do not reach full compression Locks on the database Deleting tables from the back end Transaction logs become full

Slide 14

Implement versioned editing to more SDE databases Need a more automated QA process Work on automating maintenance scripts as scheduled tasks

Slide 15

Slide 16

Administration tools in ArcGIS Python scripts ArcGIS Diagrammer GDBT for 10.0/10.1 Troubleshoot, monitor, and investigate databases Show Edits Since Reconcile Tool Generates feature class of all edits between versions Edit tracking tool

Slide 17

Slide 18

Slide 19

Slide 20

Slide 21