ArcSDE - Northeast Arc Users Group

More documents

Recommendations

Info

ArcSDE Schema and RIGeodatabase, Behaviors and Referential Integrity• ArcSDE schema “living” with or in DW schemas– You must KNOW everything about your ArcSDE and Data schemas.– “lives” alongside, integrated or “connected” into the overall Data Warehouseschemas and structures, embedded.– Need to be careful of the complex relationships and interdependencies ncies withinthe ArcSDE/GeoDatabase schema objects.• Referential Integrity and PK-FK– ArcObjects, ArcSDE and RDBMS are maintaining various pieces dependingupon the functionality (versioning, relationship classes, feature e linkedannotation, etc…) ) implemented.• Entity Integrity - define a row as a unique entity• Domain Integrity - define validity of values for columns• Referential Integrity - ensure key values are consistent across tables• User-Defined Integrity - enforce other business rules– Understand the schema and what is implemented, be careful and test.– Some customizations will work but may not necessarily be formally y supported.
Geodatabase Constructs• Consider GDB constructs when implementingbusiness logic.• Business rules modeled as geodatabase behavior• Rules stored in the database, enforced by ArcGIS– Domains enforce database integrity– Relationships enforce referential integrity– Subtypes enforce user-defined integrityRDBMSCHECK constraintPrimary keyForeign keyUser-defined procedureTriggerGeodatabaseDomain/SubtypeRelationship classSubtype, topology, geometricnetworkRelationship class withreferential integrity
Page 8 and 9:
New technologies better enablingWor
Page 10 and 11:
ESRI’s s GIS Platform
Page 12 and 13:
ArcObjects and GeodatabaseArcGIS is
Page 14 and 15:
Model Real World Features for bette
Page 16:
Processes and Workflows• With inc
Page 19 and 20:
Enterprise and Knowledge• Educati
Page 21 and 22:
Three kinds of Geodatabases1. Perso
Page 23 and 24:
Spatial Data Formats• Storing spa
Page 25 and 26:
Database ArchitecturesSQL Server 7/
Page 27 and 28:
ArcSDE Connection ArchitecturesAppl
Page 29 and 30:
Spatial Referenceby Feature Class o
Page 31 and 32:
ArcGIS Desktop HelpPrecision and Ex
Page 33 and 34:
ArcSDE data types• Storage of:- P
Page 35 and 36:
Common GIS Dataset TypesFeature Cla
Page 37 and 38:
Attribute domains, relationships, a
Page 39 and 40: Networks - To model navigation, flo
Page 41 and 42: Feature Datasets• Contain feature
Page 43 and 44: Raster Catalogs - To manage a tiled
Page 45 and 46: ArcCatalogManaging Workspaces and G
Page 47 and 48: ArcSDE client accessArcObjectsArcMa
Page 49 and 50: \arcgis\ArcSDE\Documentation\Admin_
Page 51 and 52: Primary Administrative Tables
Page 53 and 54: Storage model overview• ArcSDE fe
Page 55 and 56: Storage model overview• Versioned
Page 57 and 58: ArcSDE and Spatial column typesLAKE
Page 59 and 60: Spatial Datatype Query examplespati
Page 61 and 62: Raster Data SchemaNew at9.0
Page 63 and 64: General Storage Options• Raster D
Page 65 and 66: Raster Catalogs - To manage any ser
Page 67 and 68: Raster Columns in TablesTo hold pic
Page 69 and 70: Compressions DescribedLoss-lessLoss
Page 71 and 72: Compression Recommendations(continu
Page 73 and 74: Pyramids• Reduced resolution copi
Page 75 and 76: Pyramid Enhancements• Raster Data
Page 77 and 78: Shared• Default architecture• E
Page 79 and 80: Standalone1. Created as temporary t
Page 81 and 82: Default settings• SDE_server_conf
Page 83 and 84: What is Versioning?• Provides lon
Page 85 and 86: Versioned geodatabase• Method for
Page 87 and 88: Versions and States• Short Term v
Page 89: Integration and Performance• ArcS
Page 93 and 94: Views: Functional comparisonHeterog
Page 95 and 96: Different “windows” to datatype
Page 97 and 98: Moving or Exporting Data• Copy an
Page 99 and 100: Future - The Road Ahead“good reas
show all

ArcSDE - Northeast Arc Users Group

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

Delete template?

Save as template?