Functionality in ArcGIS Enterprise and certain apps that you use with an ArcGIS Enterprise portal depend on the use of ArcGIS Data Store. When you install ArcGIS Data Store, you choose the type of data store to create on that machine. Each data store provides different functionality within an ArcGIS Enterprise implementation.
- Relational data store—Stores feature data for hosted feature layers
- Tile cache data store—Stores caches for scene layers
- Spatiotemporal big data store—Stores feature data for spatiotemporal feature layers
- Object store—Stores cached queries for layers in hosted feature layers
The following sections list the functionality and apps that require you to use ArcGIS Data Store in your Enterprise deployment, and indicate which type of data store or stores you need to create.
Functionality
The following table lists the functionality in ArcGIS Enterprise you get with each type of ArcGIS Data Store.
| Functionality | Data store types required |
|---|---|
Configure a hosting server for ArcGIS Enterprise to allow portal members to publish hosted feature layers or add files to Map Viewer. | Relational data store |
Publish scene layers to your portal from ArcGIS Pro or a scene layer package. | Tile cache data store If you publish from ArcGIS Pro, an associated feature layer is created with the scene layer. If the associated feature layer does not reference a registered data source, the data for the associated feature layer is copied to the relational data store. |
Archive observation data streamed when using ArcGIS GeoEvent Server. | Spatiotemporal big data store |
Use GeoAnalytics Tools in Map Viewer or ArcGIS Pro. (GeoAnalytics Tools create hosted feature layers as output, and the data is stored in the spatiotemporal big data store. The portal must be configured with an ArcGIS GeoAnalytics Server.) | Spatiotemporal big data store and relational data store |
Use raster analysis tools in Map Viewer or ArcGIS Pro. Raster analysis tools require the portal to be configured for raster analysis. Raster analysis tools use the tile cache data store to temporarily store data generated during analysis. A subset of raster analysis tools create hosted feature layers, and the data for those layers is stored in the relational data store. | Relational data store |
Use location tracking with the portal or any apps that rely on location tracking, such as ArcGIS Indoors or ArcGIS Tracker. | Spatiotemporal big data store |
Create missions in ArcGIS Mission Manager. | Spatiotemporal big data store If you do not configure a spatiotemporal big data store, ArcGIS Mission Manager stores mission data in the relational data store. However, Esri highly recommends you use a spatiotemporal big data store for mission data. |
Use the Story Map Tour configurable app. | Relational data store |
Cached query responses for individual layers in hosted feature layers. Caching query responses improves drawing performance for the feature layer. | Object store |
Apps
The following Esri apps rely on the relational data store when you use the apps with an ArcGIS Enterprise portal:
If you use the ArcGIS Survey123 Web Designer to create a survey that includes layers from an ArcGIS Enterprise portal, the survey will use hosted feature layers and, therefore, relies on the relational data store.
As mentioned in the previous section, ArcGIS Mission Manager needs a spatiotemporal big data store for mission data, but it can use the relational data store if a spatiotemporal big data store is not configured.
Considerations when you need more than one type of data store
If you require more than one type of data store, Esri recommends that you configure them on separate machines. Relational and spatiotemporal big data stores each require a large percentage of a machine's memory to process data queries. Depending on the quantity and size of the data you store, each data store could consume large amounts of disk space and memory. When you put more than one type of data store on the same machine, they compete for these storage and memory resources, which can negatively affect the performance of your ArcGIS Enterprise deployment.