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.

Portal for arcgis help