Geodatabase Versioning, Replication and History - Northeast Arc ...

More documents

Recommendations

Info

Working with Schema Changes • Fault tolerant – In most cases synchronization will still execute successfully even if each replica makes schema changes – Example: If a field has been dropped, synchronization skips that field • Tools to apply schema changes across replicas – Subset of schema changes can be applied – Recommend applying schema changes across all replicas before synchronizing 2007 ESRI NEARC 92
Applying Schema Changes • Two step process – Compare replica schemas • Compare directly in a connected environment • Export replica schema to XML in a disconnected environment, send to relative replica <strong>and</strong> compare – Import the schema differences • Schema changes can be listed in different ways: – Optional – you can decide whether or not to apply the change – Can’t t Apply – these can’t t be applied 2007 ESRI NEARC 93
Page 1 and 2:
Geodatabase Versioning, Replication
Page 3 and 4:
Defining the geodatabase (GDB) •
Page 5 and 6:
Enterprise ArcSDE Geodatabase Requi
Page 7 and 8:
Editing options • Non-versioned e
Page 9 and 10:
Introducing Non-Versioned Editing N
Page 11 and 12:
No undo/redo • Edits between save
Page 13 and 14:
IT Integration • Easy to implemen
Page 15 and 16:
Introducing: Versioned Editing •
Page 17 and 18:
What is Versioning • Storing edit
Page 19 and 20:
Versioning system tables • ArcSDE
Page 21 and 22:
Editing example: User versioning ta
Page 23 and 24:
Editing example: DELETE Riverside W
Page 25 and 26:
Editing example: Save Riverside W #
Page 27 and 28:
Example: business cycle workflow DE
Page 29 and 30:
Versioning - reconcile procedure
Page 31 and 32:
Post • Synchronizes current edit
Page 33 and 34:
Overview • Geodatabases • Editi
Page 35 and 36:
Editing DEFAULT version • Start e
Page 37 and 38:
Workflow considerations • IT inte
Page 39 and 40:
Archiving 2007 ESRI NEARC 39
Page 41 and 42: Common historical queries • What
Page 43 and 44: 9.2: Geodatabase archiving • Pres
Page 45 and 46: Archive class • New feature class
Page 47 and 48: Archive time • ArcGIS represents
Page 49 and 50: Example 1: Add new feature • Edit
Page 51 and 52: Example 3: Delete feature • Delet
Page 53 and 54: Example 4: Make multiple edits and
Page 55 and 56: Answering common historical questio
Page 57 and 58: Disable archiving • If required,
Page 59 and 60: Benefits • Using DEFAULT historic
Page 61 and 62: Distributed Geodatabase (Geodatabas
Page 63 and 64: Geodatabase Replication - Use Cases
Page 65 and 66: Geodatabase Replication - LAN and W
Page 67 and 68: Distributing Data • Geodatabase R
Page 69 and 70: DBMS Replication with Geodatabases
Page 71 and 72: Check out / Check in Replication
Page 73 and 74: Two Way Replication • Requires Ar
Page 75 and 76: Replica Creation - What Data Types
Page 77 and 78: Replica Creation - Versioning • E
Page 79 and 80: Replica Synchronization • Applyin
Page 81 and 82: Connected Synchronization • Conne
Page 83 and 84: Disconnected Synchronization • At
Page 85 and 86: 2007 ESRI NEARC 85
Page 87 and 88: Replica Reconcile Policies • Thre
Page 89 and 90: What Features are Synchronized •
Page 91: Schema synchronization • Applying
Page 95 and 96: Geodatabase Replication - API • B
Page 97 and 98: Geodatabase Replication Enhancement
Page 99 and 100: Example Automation Technique • Cr
show all

Geodatabase Versioning, Replication and History - Northeast Arc ...

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?