EGMP cheat sheet
EGMP · Keep the key ideas within reach.
Enterprise geodatabase data models, constraints and supported storage
Model keys, relationships, spatial reference and quality first.
Spatial database, geodatabase and managed hosting store are distinct.
Storage/type support is version- and DBMS-specific.
Copying data must preserve the relevant schema, relationships and authority.
Branch, traditional and disconnected geodatabase workflows
Branch and traditional versioning serve different access workflows.
Named versions, default and lock scopes require actual model context.
Reconcile/post and conflict correctness are separate issues.
Classic replication, offline service sync and retained history are distinct.
Geodatabase loading, performance and recoverable maintenance
Traditional states/Compress and branch temporal maintenance differ.
Diagnose actual query/index/statistics/lock evidence.
Bulk-load speed must preserve required validation and identity.
Test recovery and coordinate consequential maintenance under authority.
ArcGIS Enterprise components, service roles and architecture boundaries
Architecture follows actual workflow and nonfunctional requirements.
Current base storage/proxy requirements differ from old four-item lists.
Federation, hosting, registered data and managed data are distinct.
Platform/version/license compatibility governs actual deployment.
ArcGIS workload capacity, availability and recoverability
Throughput and user counts require explicit workload assumptions.
Combined resource and shared-state constraints limit simple scaling.
Surviving capacity matters after the modeled failure.
HA, backup scope and tested recovery objectives are separate.
ArcGIS operational evidence, identity and controlled lifecycle changes
Trace the actual client/proxy/service/data path.
Identity, role, sharing and database authority are different layers.
Upgrade sequence and downtime depend on the supported release path.
Verify meaningful service results and preserve useful evidence.