Geodatabases Essentials Part II - s3.amazonaws.com · • Business rules, topology, networks ......

Geodatabases Essentials Part IIGeodatabases Essentials Part II

An Introduction to ArcSDE GeodatbasesAn Introduction to ArcSDE Geodatbases

Tim ClarkTim Clark

Session PathSession Path

1. Introduction to ArcSDE GeodatabasesWhat is the Geodatabase?The Geodatabase Management ApproachDifferent types of GeodatabaseWhat is an ArcSDE Geodatabase and what are its benefits?

2. Versioning3. Editing4. Archiving5. Distributed Geodatabase

What is the Geodatabase?What is the Geodatabase?

• Core ArcGIS data model– A comprehensive model for representing and managing GIS data

• A physical store of geographic data– Scalable storage model supported on different platforms

• A transactional model for managing GIS workflows

• Set of COM components for accessing data

Geodatabase Data Management ApproachGeodatabase Data Management Approach

•• The geodatabase is built on an extended relational database.The geodatabase is built on an extended relational database.–– Base relational modelBase relational model–– Base short transaction modelBase short transaction model–– Relational integrityRelational integrity–– Reliability, Flexibility, ScalabilityReliability, Flexibility, Scalability–– Supports continuous, large datasetsSupports continuous, large datasets

•• Built on the simple feature modelBuilt on the simple feature model–– Open access (OGC, C, COM, SQL)Open access (OGC, C, COM, SQL)

•• Business rules, topology, networksBusiness rules, topology, networks–– Data IntegrityData Integrity

Geodatabase Data Management Approach Geodatabase Data Management Approach ……

•• Simple features + logicSimple features + logic–– All geographic data stored as tables in a DBMSAll geographic data stored as tables in a DBMS

–– Extend functionality and data integrityExtend functionality and data integrity

–– Functionality is consistent across DBMSFunctionality is consistent across DBMS’’

•• Application logic (software) Application logic (software) –– Works on standard RDBMS tableWorks on standard RDBMS tables

–– Implements GIS integrity and behaviorImplements GIS integrity and behavior

Geodatabase Data Management Approach Geodatabase Data Management Approach ……

•• Editing and data compilationEditing and data compilation–– Rich set of editing tools Rich set of editing tools –– Maintain spatial and attribute integrityMaintain spatial and attribute integrity–– Undo and redo editsUndo and redo edits–– Multiple users editing the same dataMultiple users editing the same data

•• Versioning work flowsVersioning work flows–– Long transactionsLong transactions–– Distributed data managementDistributed data management–– ArchivingArchiving

•• Robust, customizable frameworkRobust, customizable framework–– Build and manage your own specific GIS solutionBuild and manage your own specific GIS solution

Inside the GeodatabaseInside the Geodatabase

•• A geodatabase contains datasets.A geodatabase contains datasets.–– Datasets represent collections of information with a realDatasets represent collections of information with a real--

world interpretation.world interpretation.

•• Datasets have associated information to help Datasets have associated information to help manage integrity, behavior, and interpretationmanage integrity, behavior, and interpretation

–– Domains, Relational integrity, Topology, MetadataDomains, Relational integrity, Topology, Metadata

•• Three primary datasets:Three primary datasets:–– Feature classesFeature classes–– Raster datasetsRaster datasets–– TablesTables

Feature classes

Raster datasetsTables

LinePolygon

PointDimensionAnnotation

Route

3 Types of Geodatabases3 Types of Geodatabases

•• Personal GeodatabasePersonal Geodatabase–– Single user editingSingle user editing–– Stored in MS AccessStored in MS Access–– Size limit of 2 GBSize limit of 2 GB

•• File GeodatabaseFile Geodatabase–– 1 TB per table1 TB per table–– Reduced storage requirementsReduced storage requirements

•• ArcSDE GeodatabaseArcSDE Geodatabase–– Stored in an enterprise DBMSStored in an enterprise DBMS–– Supports multiuser editing via versioningSupports multiuser editing via versioning–– Requires ArcEditor or ArcInfo to editRequires ArcEditor or ArcInfo to edit

ArcGIS

* PostgreSQL support at 9.3

PersonalGeodatabase

FileGeodatabase

ArcSDEGeodatabase

OracleSQL Server

DB2Informix

PostgreSQL*

ArcGISArcGIS

ArcSDEArcSDE

What is an ArcSDE Geodatabase? What is an ArcSDE Geodatabase?

•• ESRIESRI’’s technology for accessing and managing s technology for accessing and managing geospatial data in relational databasesgeospatial data in relational databases

•• ArcSDE Geodatabases are unique in their support of ArcSDE Geodatabases are unique in their support of the following capabilities: the following capabilities:

–– Open and interoperable across many supported DBMSsOpen and interoperable across many supported DBMSs–– Standards based, using as its native data structure the OGC Standards based, using as its native data structure the OGC

binary simple features standard and the ISO spatial type (for binary simple features standard and the ISO spatial type (for Oracle, IBM DB2, IBM Informix, and PostgreSQL only). Oracle, IBM DB2, IBM Informix, and PostgreSQL only).

–– Offers support for full, open SQL access to geodatabases Offers support for full, open SQL access to geodatabases stored in Oracle, IBM DB2, IBM Informix, and PostgreSQL. stored in Oracle, IBM DB2, IBM Informix, and PostgreSQL.

–– Full support of the Oracle format for feature storage (using Full support of the Oracle format for feature storage (using Oracle Spatial and Oracle Locator). Oracle Spatial and Oracle Locator).

ArcSDEArcSDEGeodatabaseGeodatabase

How is ArcSDE technology included in ArcGIS?How is ArcSDE technology included in ArcGIS?

UC 2006 Tech SessionUC 2006 Tech Session 1111

Operating system

DBMS

ArcSDE

Geodatabase

A

ArcObjects/ArcGIS

Personal GDB File GDB ArcSDE GDB(3 editions)

Storage format MicrosoftAccess

Folder ofbinary files

DBMS

Storage capacity 2 GB 1 TBper table*

Depends onedition

Supported O/S platform

Windows Any platform Depends onedition

Number of users Single editorMultiple readers

Single editorMultiple readers

Multiple editors& readers

Distributed GDB functionality

Check out/check inOne way replication

Check out/check inOne way replication

Replication(all types)

& versioning

3 Types of Geodatabases3 Types of Geodatabases……

When do you need an ArcSDE Geodatabase?When do you need an ArcSDE Geodatabase?

•• Users need to edit and use their data simultaneouslyUsers need to edit and use their data simultaneously

•• Need to manage long transactions and versionNeed to manage long transactions and version--based workflowsbased workflows

•• Leverage your existing relational databasesLeverage your existing relational databases

•• Require high performance and the ability to scale to Require high performance and the ability to scale to a large number of users.a large number of users.

•• Require the ability to storage extremely large Require the ability to storage extremely large amounts of dataamounts of data

What are the benefits of using an ArcSDE Geodatabase?What are the benefits of using an ArcSDE Geodatabase?

•• Leverage the underlying DBMS architecture to Leverage the underlying DBMS architecture to support: support:

–– Extremely large, continuous GIS databases Extremely large, continuous GIS databases –– Many simultaneous users Many simultaneous users –– Long transactions and versioned workflows Long transactions and versioned workflows –– Distributed and archiving based workflowsDistributed and archiving based workflows–– Relational database support for GIS data management Relational database support for GIS data management

(providing the benefits of a relational database such as (providing the benefits of a relational database such as scalability, reliability, security, backup, and integrity) scalability, reliability, security, backup, and integrity)

–– StandardsStandards--based SQL Types for Spatial when the DBMS based SQL Types for Spatial when the DBMS supports this capability supports this capability

ArcSDE for ArcGIS Desktop

ArcSDE for ArcGIS Server Workgroup

ArcSDE for ArcGIS Server Enterprise

ArcGIS Product

ArcGIS and Desktop Engine*

ArcGIS Server Workgroup ArcGIS Server Enterprise

Number of users

Max 3 users, 1 editor at any one time

Max 10 clients at one timeNo limit to the number of

connections

Unlimited

Supported DBMS

SQL Server Express 2005 SQL Server Express 2005 Oracle,SQL Server, DB2, Informix, PostGreSQL

Database limits Max database size 4 Gig1 GB RAM on a single cpu

Max database size 4 Gig1 GB RAM on a single cpu

No limits

Administration ArcGIS Desktop(ArcCatalog)

ArcGIS Desktop(ArcCatalog)

ArcGIS Desktop (ArcCatalog),

ArcSDE Commands, DBMS admin software,

Which ArcSDE Geodatabase edition?Which ArcSDE Geodatabase edition?

Scale from small, personal systems up to workgroups and very large enterprises

ArcSDE and the GeodatabaseArcSDE and the GeodatabaseClient server modelClient server model

•• All data accessed over a networkAll data accessed over a network•• All data retrieved through SQL queriesAll data retrieved through SQL queries

–– ArcSDE technology translates ArcSDE technology translates –– Spatial and attribute filters limit rows returnedSpatial and attribute filters limit rows returned

•• ArcSDE technology performs spatial filteringArcSDE technology performs spatial filteringUC2008 PreUC2008 Pre--conference Seminarsconference Seminars

Request

Geodatabase client ArcSDE

SQL query

Database server

ArcSDE and the GeodatabaseArcSDE and the GeodatabaseConnection typesConnection types

UC2008 PreUC2008 Pre--conference Seminarsconference Seminars 2020

gsrvr

GISclient

Directconnectdriver

OLE DBprovider

GISclient

GISclient

Application server Direct OLE DB

GeodatabaseGeodatabase


1. Introduction to ArcSDE Geodatabases2. Versioning

What is it?How is it used?

3. Editing4. Archiving5. Distributed Geodatabase

Versioning Versioning -- What is it?What is it?• Technology that allows multiple users to edit and

view data at the same time–Appears to users as if they have their own copy of a table

• without applying locks or duplicating data

EditorsEditors

DefaultDefault

AnalystAnalyst ReadersReaders


Versioning Workflows – How is it used

• Model what-if scenarios–Simulate situations with versions

• Example: Disaster event planning

AnalystPublic

Farmland Residential

• Editing with long transactions– Isolate work across multiple sessions

• Edits do not impact others• Example: Parcel editing

FloodPublic

• Workflow management– Create versions for project stages

• Example: Land development

A

What is a Version?What is a Version?

•• An alternate representation of the data in a geodatabaseAn alternate representation of the data in a geodatabase

•• A connection to a geodatabase is made through a A connection to a geodatabase is made through a versionversion

•• You can not create a version of a feature classYou can not create a version of a feature class–– Geodatabases are versionedGeodatabases are versioned

ParksDEFAULT Version

•• An An alternative viewalternative view of the geodatabase that has:of the geodatabase that has:––an owneran owner––a descriptiona description––a permission a permission ––a parent versiona parent version

•• Versions are not affected by changes occurringVersions are not affected by changes occurringin other versions of the databasein other versions of the database

What is a Version?

ParksQA Version

What is a Version?

•• An An alternative viewalternative view of the geodatabase that has:of the geodatabase that has:–– an owneran owner–– a descriptiona description–– a permission a permission –– a parent versiona parent version

•• Versions are not affected by changes occurringVersions are not affected by changes occurringin other versions of the databasein other versions of the database


1. Introduction to ArcSDE Geodatabases2. Versioning3. Editing

• Versioned Editing• Reconcile and Post• Non-Versioned Editing• Editing through SQL

4. Archiving5. Distributed Geodatabase

Editing DatabasesEditing Databases

•• Database editing relies on transactionsDatabase editing relies on transactions

•• Database transactions often conform to the ACID standardsDatabase transactions often conform to the ACID standards

•• Transactions have Transactions have ““ACIDACID”” standardsstandards–– AAtomictomic —— A transaction exhibits "all or nothing" behavior. A transaction exhibits "all or nothing" behavior.

–– CConsistentonsistent —— A transaction leaves the database in a consistent state.A transaction leaves the database in a consistent state.

–– IIsolationsolation —— Changes are isolated from other transactions is committed. Changes are isolated from other transactions is committed.

–– DDurableurable —— Once a transaction commits, its results are persistent.Once a transaction commits, its results are persistent.

Editing GeodatabasesEditing Geodatabases

•• Short TransactionsShort Transactions–– Small number of operations completed quicklySmall number of operations completed quickly

•• E.g. ATM transactions, Library records, TimecardsE.g. ATM transactions, Library records, Timecards–– ACID requirements through DBMS Locking mechanismsACID requirements through DBMS Locking mechanisms–– Concurrent transactions are isolated Concurrent transactions are isolated

•• Long TransactionsLong Transactions–– Large number of operations over a long time periodLarge number of operations over a long time period

•• E.g. Parcel updates, General geographic editingE.g. Parcel updates, General geographic editing–– Geodatabases extend the transaction model with VersioningGeodatabases extend the transaction model with Versioning–– Multiuser editing without locking or data duplicationMultiuser editing without locking or data duplication–– Editors work with unique isolated view of the geodatabaseEditors work with unique isolated view of the geodatabase

•• GIS editors need both long and short transactionsGIS editors need both long and short transactions

Three different ways of editing GeodatabasesThree different ways of editing Geodatabases

•• Versioned Editing (Long Transactions)Versioned Editing (Long Transactions)–– Editing in a version through ArcGISEditing in a version through ArcGIS

•• NonNon--Versioned Editing (Short Transactions)Versioned Editing (Short Transactions)–– Editing the data directly through ArcGISEditing the data directly through ArcGIS

•• Editing through SQL (Short Transactions)Editing through SQL (Short Transactions)–– Editing the data directly through SQLEditing the data directly through SQL

Versioned EditingVersioned Editing•• Versioned Edit SessionsVersioned Edit Sessions

–– Editing done through a versionEditing done through a version•• Changes tracked on delta tablesChanges tracked on delta tables

–– Support concurrent editing with long transactions (hours/days).Support concurrent editing with long transactions (hours/days).–– Undo/redo editing experience.Undo/redo editing experience.–– No locking or data extraction required.No locking or data extraction required.

Editor 1Editor 1

ReadersReaders


Work orderWork order

DefaultDefault

DesignDesign

Editor 2Editor 2

Versioned Editing Versioned Editing –– How It WorksHow It Works

•• Class must be registered as VersionedClass must be registered as Versioned–– Creates Adds and Deletes tables for tracking editsCreates Adds and Deletes tables for tracking edits


•• Adding FeaturesAdding Features–– Record added to the Adds TableRecord added to the Adds Table

–– Version will be referenced (Version will be referenced (SDE_State_ID FieldSDE_State_ID Field))


•• Deleting FeaturesDeleting Features–– Record added to Deletes TableRecord added to Deletes Table

–– Version will be referenced (Version will be referenced (Deleted_At fieldDeleted_At field))


•• Updating FeaturesUpdating Features–– Record added to both Adds and Deletes tableRecord added to both Adds and Deletes table–– Version will be referenced (Version will be referenced (SDE_State_ID FieldSDE_State_ID Field))


•• Versioned representation of a feature classVersioned representation of a feature class–– combination of records in: combination of records in:

•• Base Table, Adds Table & Deletes TableBase Table, Adds Table & Deletes Table

ArcGIS applications

Base Table

Deletes Table

Adds Table

Version Changes ViewerVersion Changes Viewer

•• Ability to see what has changed in a versionAbility to see what has changed in a version–– View changes without having to do a reconcileView changes without having to do a reconcile–– Displays all changes in version with respect to ancestor Displays all changes in version with respect to ancestor

versionversion

New at 9.3New at 9.3

Versioned Editing Versioned Editing –– Reconcile and PostReconcile and Post

•• How can versions be merged?How can versions be merged?

•• Through a process called reconcile and postThrough a process called reconcile and post

Versioned Editing Versioned Editing –– ReconcileReconcile

•• Reconcile pulls any changes from the target version Reconcile pulls any changes from the target version into the edit versioninto the edit version

•• Any conflicts will be detectedAny conflicts will be detected

Reconcile and ConflictsReconcile and Conflicts

•• Versioning does not lock data when it is editedVersioning does not lock data when it is edited–– Because of this we must make sure data is not overwrittenBecause of this we must make sure data is not overwritten–– We do this through conflict detection during a reconcileWe do this through conflict detection during a reconcile

•• A feature will be in conflict any time it has changed on A feature will be in conflict any time it has changed on both versionsboth versions

•• Conflict Resolution DialogConflict Resolution Dialog

•• Merge Geometry option for conflict managementMerge Geometry option for conflict management–– Improves the conflict management experience for:Improves the conflict management experience for:

•• large polygon and polyline featureslarge polygon and polyline features

Target VersionEdit Version

Merge

Edit Version

New at 9.3New at 9.3Reconcile and ConflictsReconcile and Conflicts

Versioned Editing Versioned Editing –– PostPost

•• Posting versions merges any changes in the edit Posting versions merges any changes in the edit version into the target versionversion into the target version

–– After a post versions are identicalAfter a post versions are identical

Versioned Editing Versioned Editing -- Move to Base OptionMove to Base Option

•• What is it? What is it? –– Versioned editing with the ability to move changes made in Versioned editing with the ability to move changes made in

the Default version into the base tablesthe Default version into the base tables–– Changes made in nonChanges made in non--Default versions are still stored in the Default versions are still stored in the

delta tablesdelta tables•• Designed for IT integrationDesigned for IT integration

–– Edits visible to 3rd part applications as soon as they are Edits visible to 3rd part applications as soon as they are savedsaved

•• Simple data onlySimple data only–– Points, lines, polygons, annotation, relationship classesPoints, lines, polygons, annotation, relationship classes–– No Topology, Geometric NetworksNo Topology, Geometric Networks……etcetc

Versioned Editing Versioned Editing -- Move to BaseMove to Base

•• Why would I use the move to base option?Why would I use the move to base option?–– Want version editing experience butWant version editing experience but……

•• Need to integrate with 3Need to integrate with 3rdrd party applicationsparty applications•• Use of database constraints when editing DEFAULT versionUse of database constraints when editing DEFAULT version

ArcGISArcGISEditingEditing

AnalystAnalyst

33rdrd partypartyApplicationApplication


DefaultDefault

NonNon--Versioned EditingVersioned Editing•• Directly editing the database tablesDirectly editing the database tables

–– Not editing in a versionNot editing in a version•• Uses a database transaction (short transaction)Uses a database transaction (short transaction)•• Edits immediately available upon saveEdits immediately available upon save

–– Designed for IT integrationDesigned for IT integration•• Suggested for NonSuggested for Non--ESRI client interactionESRI client interaction•• Database integrity rulesDatabase integrity rules

–– Simple data onlySimple data only•• Points, lines, polygons, annotation, relationship classesPoints, lines, polygons, annotation, relationship classes•• No Topology, Geometric NetworksNo Topology, Geometric Networks……etcetc

EditorsEditors ReadersReaders

SQL EditingSQL Editing

• SQL can be used to update data directly

• Geometry editing possible through spatial types• What is a spatial type?

–A database data type that stores spatial data • Why are they useful?

–ESRI Client not necessary to edit data–SQL access to geometries

• Databases with spatial types–Oracle, SQL Server, Informix, DB2, PostgreSQL

Geodatabase Editing SummaryGeodatabase Editing Summary

•• Three ways to edit dataThree ways to edit data–– Versioned Editing (Long Transactions)Versioned Editing (Long Transactions)

–– NonNon--Versioned Editing (Short Transactions)Versioned Editing (Short Transactions)

–– Editing through SQL (Short Transactions)Editing through SQL (Short Transactions)

•• Which one do I use? Which one do I use? –– Depends on behavior desiredDepends on behavior desired

•• Short vs Long TransactionsShort vs Long Transactions

•• Is data being accessed by nonIs data being accessed by non--ESRI applications?ESRI applications?

•• Are many editors editing the same data?Are many editors editing the same data?

Version Editing Demo


1. Introduction to ArcSDE Geodatabases2. Versioning3. Editing4. Archiving

• What is it?• How is it used?

5. Distributed Geodatabase

Geodatabase Archiving: What is it?Geodatabase Archiving: What is it?

•• Historical archiving of all edits made Historical archiving of all edits made to the Default versionto the Default version

–– Maintain a record of a feature classes Maintain a record of a feature classes representation over timerepresentation over time

•• Ability to query historical Ability to query historical representations of a featurerepresentations of a feature

–– Archives can be queried based on date Archives can be queried based on date informationinformation

•• Extends versioningExtends versioning–– Classes must be versioned before they Classes must be versioned before they

can be archive enabledcan be archive enabled TimeTime

Geodatabase Archiving: How it worksGeodatabase Archiving: How it works

•• Class must be enabled for archivingClass must be enabled for archiving–– This creates an archive table in the geodatabaseThis creates an archive table in the geodatabase–– Size of archive table depends on size of class being Size of archive table depends on size of class being

archivedarchived

5252

F T

Archive Table

Enable Archiving

Base Table

Delta Tables

Adds

Deletes

A

GDB_FROM_DATE

GDB_TO_DATE


5353

F T

Archive TableBase Table

Delta Tables

Adds

Deletes

•• When edits are made on the Default versionWhen edits are made on the Default version–– These changes are added to the archive tableThese changes are added to the archive table

A


•• Archive table is used to satisfy historical queriesArchive table is used to satisfy historical queries

•• Can navigate through history in two waysCan navigate through history in two ways–– Through specific date queryThrough specific date query–– Through historical markerThrough historical marker

5454A

Archiving Demo

Archiving in a nutshell


1. Introduction to ArcSDE Geodatabases2. Versioning3. Editing4. Archiving5. Distributed Geodatabase

• Data Distribution and Geodatabase Replication

Geodatabase ReplicationGeodatabase Replication

•• Allows you to distribute copies of data across 2 or Allows you to distribute copies of data across 2 or more geodatabasesmore geodatabases

•• You can edit the databases independently and You can edit the databases independently and synchronize them as needed.synchronize them as needed.

•• Released at 9.2 Released at 9.2 -- Builds upon disconnected editing Builds upon disconnected editing from earlier releases (8.3)from earlier releases (8.3)

UC 2007 Tech SessionsUC 2007 Tech Sessions 5757

Replication Replication –– Use CasesUse Cases

•• Mobile Users and Field Crews who need to be disconnected Mobile Users and Field Crews who need to be disconnected from the network.from the network.

•• Users who need to maintain copies of data at different Users who need to maintain copies of data at different organizational levels (city, county, state)organizational levels (city, county, state)

•• Users who want to maintain copies of data at different Users who want to maintain copies of data at different geographic facilities. geographic facilities.

•• Users who need to distribute work to contractors.Users who need to distribute work to contractors.

•• Production and publication geodatabasesProduction and publication geodatabases


Distributed Geodatabase Use CasesDistributed Geodatabase Use Cases

Multiple levels

LocalLocal LocalLocal LocalLocal LocalLocal LocalLocal LocalLocal LocalLocal LocalLocal LocalLocal

RegionalRegionalOfficeOffice



MainMainOfficeOffice

Regional Offices

OfficeOffice

OfficeOffice OfficeOffice

OfficeOfficeOfficeOffice

OfficeOffice

Production / Publication

PublicationPublication

ArcGISServerArcGISServer

ReadersReaders

EditorsEditors

ProductionProduction

Mobile Users

CentralCentralOfficeOffice

Multiple levels

LocalLocal LocalLocal LocalLocal LocalLocal LocalLocal LocalLocal LocalLocal LocalLocal LocalLocal




MainMainOfficeOffice

Regional Offices

OfficeOffice

OfficeOffice OfficeOffice

OfficeOfficeOfficeOffice

OfficeOffice

Production / Publication

PublicationPublication

ArcGISServerArcGISServer

ReadersReaders

EditorsEditors

ProductionProduction

Mobile Users

CentralCentralOfficeOffice

Data distribution in Enterprise systemsData distribution in Enterprise systems

•• Geodata services can be used in conjunction Geodata services can be used in conjunction with other data distribution techniqueswith other data distribution techniques


–– Use geodata Use geodata servicesservices for field workers for field workers who need ArcGIS Desktop or ArcGIS who need ArcGIS Desktop or ArcGIS Engine in the fieldEngine in the field

Mainoffice

Web services

–– Use Mobile services for field workers with Use Mobile services for field workers with lightweight mobile deviceslightweight mobile devices

–– Use geodatabase replication to synchronize Use geodatabase replication to synchronize changes between officeschanges between offices

Regionoffice

Geodatabase Replication Geodatabase Replication -- ConceptsConcepts

•• A Child Replica is created from a Parent Replica.A Child Replica is created from a Parent Replica.

•• You can replicate :You can replicate :–– A specific version.A specific version.–– Specific datasets.Specific datasets.–– A subset of features in the chosen datasetsA subset of features in the chosen datasets


Parent Replica_AParent Replica_A

Child Replica_AChild Replica_A

Geodata Services: replica typesGeodata Services: replica types


One-way

Two-wayMultiple times

editsChild

geodatabaseParent

geodatabase

Multiple times

editsChild

geodatabaseParent

geodatabase

Checkout/ check-in

Once only

edits Child geodatabase

Parentgeodatabase

Replication Replication -- ConceptsConcepts

•• Works in a connected and a disconnected environmentWorks in a connected and a disconnected environment

•• Replicas can be Synchronized in either both directions or just Replicas can be Synchronized in either both directions or just a single directiona single direction

•• Synchronization is based on exchanging messages and is fault Synchronization is based on exchanging messages and is fault toleranttolerant

•• You can Create and Synchronize Replicas using Wizards and You can Create and Synchronize Replicas using Wizards and GP ToolsGP Tools

•• Supports a applying schema changes across replicas Supports a applying schema changes across replicas –– Subset of schema changes are supportedSubset of schema changes are supported

•• Developers have a high level object model and APIDevelopers have a high level object model and API


Geodatabase Replication Geodatabase Replication -- LAN and WANLAN and WAN

•• LAN LAN -- Use connections to your local geodatabases Use connections to your local geodatabases

•• WAN WAN -- Use ArcGIS Server and geodata web services Use ArcGIS Server and geodata web services to access remote geodatabasesto access remote geodatabases

•• All geodatabase replication workflows are supported All geodatabase replication workflows are supported in both environmentsin both environments


9.3 Geodatabase Replication9.3 Geodatabase Replication

•• Enhanced one way replication to support replicating Enhanced one way replication to support replicating to file geodatabases and personal geodatabasesto file geodatabases and personal geodatabases

•• Added logging to improve trouble shootingAdded logging to improve trouble shooting

•• User defined global IDUser defined global ID’’s (API)s (API)

•• Make it easier to generate updategrams (API) Make it easier to generate updategrams (API)


Geodatabase Replication Geodatabase Replication –– Getting StartedGetting Started

•• Anticipate future needs when defining the data to Anticipate future needs when defining the data to replicatereplicate

•• Have a well defined data model before creating Have a well defined data model before creating replicasreplicas

•• Choose the right replica typeChoose the right replica type–– Consider 2 way replicas with ArcSDE for Microsoft SQL Server Consider 2 way replicas with ArcSDE for Microsoft SQL Server

Express instead of checkExpress instead of check--out replicasout replicas–– Use 1 way replicas over 2 way replicas when possibleUse 1 way replicas over 2 way replicas when possible



•• Use models or scripts for replicas you plan to create Use models or scripts for replicas you plan to create on a regular basison a regular basis

–– You can use the create replica and create replica from server You can use the create replica and create replica from server geoprocessing tools to build modelsgeoprocessing tools to build models

•• Consider using the following replica creation Consider using the following replica creation optionsoptions

–– ReRe--use schema (checkuse schema (check--out replicas) out replicas) –– uses existing schemauses existing schema–– Register only Register only –– replicates prereplicates pre--copied datacopied data–– Relationship classes processing is optionalRelationship classes processing is optional

•• Schedule SynchronizationsSchedule Synchronizations–– You can use geoprocessing models exported to python and the You can use geoprocessing models exported to python and the

windows schedulerwindows scheduler–– Consider synchronization orderConsider synchronization order



•• Integrate synchronization with version management Integrate synchronization with version management strategy strategy

–– Synchronize before running reconcile and compress servicesSynchronize before running reconcile and compress services–– Reconcile service should cover replicas with a manual reconcile Reconcile service should cover replicas with a manual reconcile

policy policy

•• Network speedNetwork speed–– Use geodatabases directly over fast networks (LAN) Use geodatabases directly over fast networks (LAN) –– Use ArcGIS server and geodata services on slower networks (WAN Use ArcGIS server and geodata services on slower networks (WAN

–– i.e. DSL)i.e. DSL)–– Use disconnected synchronization techniques over very slow Use disconnected synchronization techniques over very slow

networks (slow dialnetworks (slow dial--up modem) or where there is no network up modem) or where there is no network connectivityconnectivity


DBMS Replication with GeodatabasesDBMS Replication with Geodatabases

•• Geodatabase replication does not use DBMS Geodatabase replication does not use DBMS replicationreplication

•• DBMS Replication DBMS Replication -- Requirements and limitationsRequirements and limitations–– Requires knowledge of how the geodatabaseRequires knowledge of how the geodatabase\\ArcSDE system ArcSDE system

tables work tables work –– No tools provided in ArcGIS to support itNo tools provided in ArcGIS to support it–– Limited support for cross DBMS replicationLimited support for cross DBMS replication–– Does not support or has limited support for complex geodatabase Does not support or has limited support for complex geodatabase

data types and limited filters to define the data to replicatedata types and limited filters to define the data to replicate

•• DBMS Replication DBMS Replication -- AdvantagesAdvantages–– Can work with nonCan work with non--versioned dataversioned data–– Can replicate entire databaseCan replicate entire database–– Can be configured to provide synchronous replicationCan be configured to provide synchronous replication–– Ideal for systems requiring high availabilityIdeal for systems requiring high availability


Geodatabase ReplicationGeodatabase Replication


DemoDemo

WhatWhat’’s coming: Geodatabase Replications coming: Geodatabase Replication

•• One way replication using archivingOne way replication using archiving•• One way child to parent replicaOne way child to parent replica•• Schema mapping across replicasSchema mapping across replicas•• Simple checkSimple check--out and twoout and two--way replicasway replicas•• Extending XML UpdateExtending XML Update--gram format to store the gram format to store the

original/old row original/old row •• Create a replica to a named version on the childCreate a replica to a named version on the child


Geodatabase SummaryGeodatabase Summary

•• ArcSDE Geodatabases allow you to:ArcSDE Geodatabases allow you to:–– Manage geographic informationManage geographic information

–– Work with rich data models that go beyond simple features, Work with rich data models that go beyond simple features, rasters, and attributesrasters, and attributes

–– Openly manage transactions, archives, and replicas across Openly manage transactions, archives, and replicas across organizationsorganizations

–– Openly edit in any application using simple features Openly edit in any application using simple features interchangeinterchange

Learn Morehttp://www.esri.com/training

InstructorInstructor--Led TrainingLed Training

ESRI Training…keep critical skills up to date

Building GeodatabasesIntroduction to the Multiuser GeodatabaseData Management in the Multiuser

GeodatabaseManaging Editing Workflows in a Multiuser

Geodatabase

Geodatabases Essentials Part II - s3.amazonaws.com · • Business rules, topology, networks ......

Documents

Transcript of Geodatabases Essentials Part II - s3.amazonaws.com · • Business rules, topology, networks ......