Data Stores, Content Management, and Publishing
What this domain tests
This domain tests which data store type backs which layer, when to copy data versus reference it, and how portal content and services correspond.
Data store types
- Relational: a managed PostgreSQL enterprise geodatabase holding hosted feature layers and feature collections; one primary plus an optional standby, not a scale-out cluster.
- Tile cache: hosted tile layers and cached tiles; can span multiple machines.
- Spatiotemporal: large hosted layers used by GeoAnalytics workloads; can span multiple machines.
- Graph: backs ArcGIS Knowledge.
Hosted versus referenced
Hosted layers copy data into the managed data store: the publisher controls the data, offline and sync work, and the source database is no longer needed. Referenced layers read registered data live: register the enterprise geodatabase, file share or cloud store with the hosting server, then publish from ArcGIS Pro using the same connection. Referenced suits large, frequently refreshed authoritative data; hosted suits editing, sync and self-contained content.
Content management
Items live in folders, are shared through groups, can be categorized, marked authoritative or deprecated, and protected from deletion. Each hosted service has a matching item, so overwriting an item republishes instead of duplicating.
Worked example
A 60 GB parcel layer in SQL Server is refreshed nightly and must be served without a nightly copy. Reasoning: publishing hosted would copy 60 GB every night and double storage. Instead register the enterprise geodatabase as a data store on the hosting server using the same connection file, publish a referenced feature layer from Pro, and grant the publishing account read privileges on the source. Because field crews also need offline editing, publish a second, smaller hosted layer for the editable subset only.
Traps
Expecting the relational data store to scale out like the tile cache; connecting SQL clients to the managed geodatabase; forgetting that referenced layers need privileges granted in the source database; assuming the data store upgrades itself when ArcGIS Server is upgraded.