Skip to main content

File geodatabases

A file geodatabase is a collection of files in a folder on disk that can store, query, and manage spatial and nonspatial data. Create a file geodatabase in a project folder or use the Create File Geodatabase geoprocessing tool.

Datasets in file geodatabases

File geodatabases contain system tables that provide geodatabase functionality as well as the data you add to the geodatabase. The data you add can be stored in the following types of datasets:

  • Catalog datasets

  • Feature classes

  • Feature datasets

  • Mosaic datasets

  • Oriented imagery datasets

  • Raster datasets

  • Tables (nonspatial)

  • Trajectory datasets

Feature classes and tables can contain subtypes and attachments, and you can relate them to one another using relationship classes.

Feature datasets can contain feature classes as well as the following types of datasets:

  • Geometric networks (read-only in ArcGIS Pro)

  • Network datasets (requires the ArcGIS Network Analyst extension)

  • Parcel fabrics

  • Terrains (requires the ArcGIS 3D Analyst extension)

  • Topologies

  • Trace networks

  • Utility networks

File geodatabases can also contain domains and views, and they can participate in checkout/check-in and one-way replication.

Several clients can access the data in the same file geodatabase simultaneously. However, they cannot edit the same dataset simultaneously.

File geodatabases and protected access

A file geodatabase is a workspace that contains one or more datasets. When protected access for Microsoft OneDrive files is enabled, file access and checkout status are applied to the file geodatabase workspace rather than to individual datasets. As a result, the OneDrive status of the file geodatabase workspace can affect access to all datasets stored in the file geodatabase.

This behavior reflects the way file geodatabases are designed. A file geodatabase consists of a collection of related files that work together as a single workspace. Managing access at the workspace level helps maintain consistency across those files and helps protect the geodatabase from simultaneous modifications by multiple users.

When a user adds a feature class or table to a map from a protected file geodatabase, the entire file geodatabase workspace is checked out to that user. Other users can continue to access the datasets that reside in that file geodatabase in a read-only state until the data is checked back in. However, if the file geodatabase is actively being edited, it may be temporarily unavailable to other users until the edits are completed and changes have been synchronized to the cloud.

Learn more about working with protected data

Learn more about working with geodatabases stored in OneDrive and SharePoint locations

Data management in file geodatabases

The default maximum size of datasets in file geodatabases is 1 TB. You can increase the maximum size to 256 TB for large datasets. This is controlled by a configuration keyword. For more information about size limits, see File geodatabase size and name limits.

You can compress datasets in a file geodatabase to save space, but doing so makes the datasets read-only. If the data in your file geodatabase is edited frequently, consider compacting the file geodatabase to clean up storage and unused space, thereby reducing the geodatabase size.

To control how other people use the data you send to them in a file geodatabase, you can apply a license to the file geodatabase before you give it to them.