Professional Documents
Culture Documents
Rob McPherson
In this hour.
Use of the case tools for schema design Maintenance of the schema Migration of the schema
ArcGIS Architecture
Overriding Idea. The more use we make of the Geodatabase functionality, the more important it is that the Geodatabase schema is managed using ArcCatalog and not the underlying database tools.
ESRI kb article describes set up http://support.esri.com/index.cfm?fa=knowledg ebase.techarticles.articleShow&d=26105 Open new document using ESRI template
UML Demo
ArcSDE repository
ArcCatalog/ArcSDE may have created entries in Table_Registry, Layers, Geometry_Columns, Spatial_references, GDB_Objectclasses, GDB_FeatureClasses, GDB_FieldInfo, Column_registry, GDB_Tables_Last_Modified, GDB_Subtypes, GDB_RelClasses, GDB_TopoClasses
Column_Registry
ArcSDE 9.0/9.1 maintains its own dictionary.
Reduces chatter with the database dictionary Allows caching of values Do not make changes outside the ArcGIS toolset If changes are made, connect as the schema owner in arccatalog and access the changed class to realign the dictionary Register all tables in your geodatabase ArcSDE will look in Column registry first and then the dictionary.
We cannot
Versions, Networks and Topologies Topologies and networks may need to be dropped and recreated to allow schema changes Versioned datasets and classes may need to be unversioned. Care must be taken to avoid loss of data. If there are edits a perfect compress will be needed prior to unversioning.
Schema Migration
In this last section we will look at
Issues around copying the schema to a new database e.g. moving from test to production Options for copying data between geodatabases
Generate the final XML, Apply it to the source database and save the XML which will now be updated with all the projection information
Permissions, Versioning and Topologies Permissions are very difficult to recreate after the event Keep a script of permissions so that the same permissions are applied in production Use roles not users to apply permissions. This allows the Test and Prod users to change but the permissions to remain the same Model build or script all versioning and Topologies and maintain these models so that the production database matches the test database
Transferring Data
Small amounts of static data are ideal for transferring using XML If the class exists in the production database i.e. it will be created by the model, use an XML recordset If the class does not exist use an XML workspace to create the class and populate it
Transferring Data
To transfer Large volumes of data consider SDEExport
Version aware so there is no need to compress Creates compressed output Can be used to transfer between versions and databases with limitations Fast server side process
SDE Export
Problems
SdeExport is not Geodatabase aware Feature datasets will not be maintained Annotation and Dimensions will not register correctly Metadata is not transferred
Solutions
Pre-create the classes feature classes in feature datasets, Annotation classes etc Use sdeimport o append to load into these precreated classes Use ArcCatalog if metadata or feature linked annotation must be copied
Conclusion
Start with a UML model and keep it up to date throughout the development Use Model builder or scripting to secure configuration which will need to be repeated when a migration happens Use ArcGIS tools for all schema management If it goes wrong dont fiddle - use the ArcGIS tools to put it right.
Resources
ESRI White papers ESRI Inc produce an Instructor led course on Geodatabase modelling using Case Tools
We have not yet had enough demand to run this course!
Questions