The default maximum size of datasets in file geodatabases is 1 TB. User data can be stored in the following types of datasets:įeature datasets can contain feature classes as well as the following types of datasets:
#Arcgis file geodatabase plus
FileGDB Formatįile geodatabases are made up of seven system tables plus user data. gdb file to manage spatial as well as non-spatial data. gdb file in the same directory for it to work. It requires certain other files to be kept alongside the. This is not usually a recommended projection for storing your datasets in an enterprise geodatabase, but it is a good projection for caching a web map from a file geodatabase.ESRI file Geodatabase (FileGDB) is a collection of files in a folder on disc that hold related geospatial data such as feature datasets, feature classes and associated tables. A common example is caching a web map in the WGS 1984 Web Mercator (Auxiliary Sphere) projection used by ArcGIS Online, Bing Maps, and Google Maps. You can even replicate into the projection of the map that will be cached. You can use one-way replication from an enterprise geodatabase to create these file geodatabases. This can lighten the load on your database and speed up caching. By placing an identical file geodatabase on each machine working on the cache, you can eliminate multiple calls to the enterprise geodatabase that would need to occur across the network. File geodatabases and map cachingįile geodatabases work well for map caching scenarios. You can release the geodatabase by stopping the service or, for multiple-machine sites, by temporarily removing the ArcGIS Server machines from the site, and reconnecting them after the file geodatabase has been updated.ĪrcGIS Server cannot disable schema locking on file geodatabases. Also, in scenarios in which the file geodatabase is a publication geodatabase (in one-way replication workflows), replica synchronization needs to occur during periods of inactivity in the map service or by releasing the file geodatabase from being used by the map service.
Because of this, you cannot publish feature services that reference data in a file geodatabase. Factors that influence potential disk I/O contention for a shared file geodatabase include the number of layers in the map service, the nature of the data in the file geodatabase, and the file storage device.įile geodatabases are intended for read-only use with ArcGIS Server.
This configuration minimizes network communication traffic among the different ArcGIS Server components and reduces I/O contention when accessing the file geodatabases. Do not configure the ArcGIS Server site to access a single file geodatabase over the network. For example, in an ArcGIS Server site with three machines, each machine must access its own copy of the file geodatabase. When you use a file geodatabase as a data source, place an identical copy of the file geodatabase on each ArcGIS Server machine. Also, standard database management system capabilities, such as logging, backup and recovery, and failover configuration, are not available in file geodatabases. In map and globe caching workflows for which many read-only calls are being made to the data in rapid succession, file geodatabases accessed through local paths often perform better than enterprise geodatabases.īefore you choose to use a file geodatabase, remember that some functionality of enterprise geodatabases, such as versioning, geodatabase replication, and historical archiving, are not available in file geodatabases. Depending on the characteristics of the GIS data, a file geodatabase may perform better than an enterprise geodatabase if the database the enterprise geodatabase is stored in is not optimized and maintained. File geodatabases generally provide good performance without needing extra configuration or tuning. If your organization does not have a database administrator on staff and your published data is relatively static, using a file geodatabase may be a good alternative. However, this recommendation is provided with the assumption that your organization has a dedicated database administrator to optimize, tune, and maintain the database. An enterprise geodatabase offers high-availability support, backup and recovery, concurrency, scalability, and a tendency to provide superior throughput. It is generally recommended that you use an enterprise geodatabase to maintain the source data for your map and feature services. When to use an enterprise geodatabase versus a file geodatabase
This topic discusses some appropriate scenarios for using enterprise geodatabases and file geodatabases. When deploying an ArcGIS Server site, you need to choose where to place the source data for your web services. When to use an enterprise geodatabase versus a file geodatabase.