Dataset system tables

When you query your database using database management system or SQL tools, you'll see geodatabase dataset tables. All the tables that compose a single dataset are stored in the schema of the database user who created the dataset.

The tables created for each type of dataset supported in an enterprise geodatabase are listed here so you can identify them. Do not alter these tables using SQL.

Catalog datasets

A catalog dataset is a table in the geodatabase that stores references to other data sources. This allows you to organize data items.

The catalog dataset's object ID is stored in the gdb_items system table. In the Definition field of the gdb_items system table, the XML definition stores the value for the Feature Type value is esriFTCatalogDatasetItem.

Feature datasets

Feature datasets are objects that allow you to implement specific geodatabase dataset types, such as networks or topologies. A feature dataset is not a separate table in the database; it is a virtual collection of feature classes and controller (or extension) datasets that are grouped by a common ID. The ID is maintained in the gdb_items system table. Each feature class is identified as part of the feature dataset through the gdb_itemrelationships system table.

Geometric networks

Geometric networks are collections of line (edge) and point (junction) feature classes in a feature dataset that possess a connectivity relationship. Geometric networks are legacy dataset types used to model utility infrastructure, such as electric lines and sewer systems.

You cannot create geometric networks in ArcGIS Pro, but you can view them.

The number of tables varies depending on the elements the network contains. A maximum of 21 tables can be created for a geometric network that contains turns and weights.

The asterisk (*) in the following list denotes tables that are always created for a geometry network. The ID in the table names is the logical network ID, which is stored in the gdb_items system table.

  • n_<id>_desc*
  • n_<id>_e<#>*
  • n_<id>_edesc
  • n_<id>_estatus*
  • n_<id>_etopo*
  • n_<id>_flodir*
  • n_<id>_j<#>
  • n_<id>_jdesc*
  • n_<id>_jstatus*
  • n_<id>_jtopo*
  • n_<id>_jtopo2
  • n_<id>_props*
  • n_<id>_t<#>
  • n_<id>_tdefn
  • n_<id>_tdefn2
  • n_<id>_tdesc
  • n_<id>_tstatus

Network datasets

Network datasets are collections of feature classes that possess a connectivity relationship. Network datasets are created using three types of sources—edge feature sources, such as street centerlines; junction feature sources, such as point feature classes containing railroad crossings; and turn feature sources. They are used to model transportation.

You cannot create or update network datasets in ArcGIS Pro, but you can view them.

The following tables store network dataset information. The ID in the first six tables is the logical network identifier. The itemID in the last two tables is the object ID of the network in the gdb_items system table.

  • n_<id>_desc
  • n_<id>_edgeweight
  • n_<id>_junctionweight
  • n_<id>_props
  • n_<id>_topology
  • n_<id>_turnweight
  • nd_<itemid>_dirtyareas
  • nd_<itemid>_dirtyobjects

Utility networks

A utility network is a set of interrelated tables in an enterprise geodatabase that provides a framework for modeling utility systems such as electric, gas, water, storm water, wastewater, and telecommunications.

You create utility networks in enterprise geodatabases using ArcGIS Pro and publish the networks to an ArcGIS GIS Server site federated with an ArcGIS Enterprise portal. The other members of your organization interact with the network through the portal item, not the layer in the geodatabase.

The following are the tables that compose a utility network. Some of the tables are generated the first time you perform an operation that requires the table's existence. The ID in the table names is the oid value from the gdb_items system table.

  • un_<id>_aggregations
  • un_<id>_associations
  • un_<id>_attributeoverrides
  • un_<id>_connectivityoverrides
  • un_<id>_containers
  • un_<id>_diagrams
  • un_<id>_dirtyareas
  • un_<id>_edgeweights
  • un_<id>_edges
  • un_<id>_eidmappings
  • un_<id>_elementassociations
  • un_<id>_junctionweights
  • un_<id>_junctions
  • un_<id>_lineerrors
  • un_<id>_pointerrors
  • un_<id>_polygonerrors
  • un_<id>_props
  • un_<id>_relations
  • un_<id>_rules
  • un_<id>_subnetworks
  • un_<id>_systemjunctions
  • un_<id>_templates
  • un_<id>_tmpaggregations
  • un_<id>_tmpcontainers
  • un_<id>_tmpdiagrams
  • un_<id>_tmpedges
  • un_<id>_tmpjunctions
  • un_<id>_tmprelations
  • un_<id>_topology
  • un_<id>_traceconfigurations
  • un_<id>_weightdefs

Trace networks

A trace network is a set of interrelated tables that provides a framework for modeling linear systems such as railroads and hydrology systems.

The following are the tables that compose a trace network. Some of the tables are generated the first time you perform an operation that requires the table's existence. The ID in the table names is the oid value from the gdb_items system table.

  • tn_<id>_aggregations
  • tn_<id>_associations
  • tn_<id>_containers
  • tn_<id>_diagrams
  • tn_<id>_dirtyareas
  • tn_<id>_edgeweights
  • tn_<id>_edges
  • tn_<id>_eidmappings
  • tn_<id>_elementassociations
  • tn_<id>_junctionweights
  • tn_<id>_junctions
  • tn_<id>_lineerrors
  • tn_<id>_pointerrors
  • tn_<id>_props
  • tn_<id>_relations
  • tn_<id>_systemjunctions
  • tn_<id>_templates
  • tn_<id>_tmpaggregations
  • tn_<id>_tmpcontainers
  • tn_<id>_tmpdiagrams
  • tn_<id>_tmpedges
  • tn_<id>_tmpjunctions
  • tn_<id>_tmprelations
  • tn_<id>_topology
  • tn_<id>_traceconfigurations
  • tn_<id>_weightdefs

Parcel fabrics

Parcel fabrics are a type of dataset in the geodatabase that is created and maintained using data from survey plans. The fabric is a continuous, integrated surface of connected parcels representing the complete survey record for an area of land. The dataset contains several feature classes. These feature classes represent the boundaries, endpoints, and other physical attributes of parcels.

There are two parcel fabric implementations: ArcGIS parcel fabrics that are accessed through feature services and ArcMap parcel fabrics.

ArcGIS parcel fabrics

The following tables are created in the database when you create a parcel fabric in ArcGIS Pro:

  • <parcel_fabric>_connections
  • <parcel_fabric>_points
  • <parcel_fabric>_records

These tables, along with the feature class tables required for the parcel fabric type and attribute rule validation tables, are visible in ArcGIS Pro and the database.

ArcMap parcel fabrics

Legacy parcel fabrics are accessed in the geodatabase directly from ArcMap. These types of parcel fabrics are read-only in ArcGIS Pro.

The following tables in the database are part of an ArcMap parcel fabric:

  • <parcel_fabric>_accuracy
  • <parcel_fabric>_adjustments
  • <parcel_fabric>_control
  • <parcel_fabric>_history
  • <parcel_fabric>_idsequencer
  • <parcel_fabric>_jobobjects
  • <parcel_fabric>_jobs
  • <parcel_fabric>_levels
  • <parcel_fabric>_linepoints
  • <parcel_fabric>_lines
  • <parcel_fabric>_parcels
  • <parcel_fabric>_plans
  • <parcel_fabric>_points
  • <parcel_fabric>_vectors


Topologies are rules that enforce data integrity and manage the behavior of spatially related feature classes. A geodatabase topology stores information about the feature classes that participate in the topology, the cluster tolerance assigned to the topology, the relative rank of each feature class in the topology, and a list of the rules that apply to that topology.

When you validate a topology, the dirty areas and topology errors identified for the topology are stored in a set of tables in the schema of the user connected to the geodatabase when topology validation is performed.

The following are the tables that compose a topology. The ID in the table names is the topology identifier stored in the gdb_items system table.

  • t_<id>_dirtyareas
  • t_<id>_lineerrors
  • t_<id>_pointerrors
  • t_<id>_polyerrors

Terrain datasets

Terrain datasets are surfaces that represent three-dimensional space. They use measurements (stored as feature classes) and rules to generate triangulated irregular network (TIN) pyramids to represent elevation. The source feature classes can be referenced by the terrain dataset or embedded in the terrain dataset.

The following internal tables are part of a terrain dataset:

  • dtm_<objectID>_compositetiles
  • dtm_<objectID>_dirtyarea
  • dtm_<objectID>_embed_#—Only present if the terrain dataset contains embedded data. One table exists per embedded feature class in the terrain dataset.
  • dtm_<objectID>_insidetiles
  • dtm_<objectID>_mrfc
  • dtm_<objectID>_props

Mosaic datasets

Multiple tables that store information about the imagery that is stored on disk are used to implement mosaic datasets. A set of properties and rules in the tables defines a real-time mosaic view of the imagery data. The dataset name is the middle part of the system table names.

There can be up to 12 tables in a mosaic dataset. Some of the tables are generated the first time you perform an operation that requires the table's existence. Referenced mosaic datasets only have two tables: the BND and LOG tables. The tables are as follows:

  • amd_<dataset_name>_ana
  • amd_<dataset_name>_art
  • amd_<dataset_name>_bnd
  • amd_<dataset_name>_cat
  • amd_<dataset_name>_cca
  • amd_<dataset_name>_che
  • amd_<dataset_name>_csl
  • amd_<dataset_name>_log
  • amd_<dataset_name>_ovr
  • amd_<dataset_name>_sml
  • amd_<dataset_name>_str
  • amd_<dataset_name>_sts

Raster datasets

Raster data is spatial data represented in an array of equally sized cells arranged in rows and columns. Raster data is composed of one or more raster bands. When you create or import a raster dataset, a raster column is added to the base table when it is created in the database. Each cell of the raster column contains a reference to a raster stored in a separate raster table.

Each raster dataset contains a base table that stores attributes, a raster column, and the footprint (the area) of the raster.

Raster images and properties are stored in the following tables:

  • sde_aux_<raster_column_ID>
  • sde_blk_<raster_column_ID>
  • sde_bnd_<raster_column_ID>
  • sde_ras_<raster_column_ID>
  • sde_vat_<raster_column_ID>—Optional table to define attributes for raster cell values of a raster dataset.

Trajectory datasets

Trajectory datasets store a collection of files and data points that represent the orbital path of a satellite.

In addition to the dataset you see in ArcGIS Pro, four tables in the user's schema store information about each trajectory dataset. The <dataset_name> portion of the system tables is the same as the name of the trajectory dataset.

  • amd_<dataset_name>_art
  • amd_<dataset_name>_bnd
  • amd_<dataset_name>_cat
  • amd_<dataset_name>_def
  • amd_<dataset_name>_log


Toolboxes store geoprocessing tools and scripts. You can create a toolbox in a geodatabase to store the system geoprocessing tools you use often and custom scripts that you create.

For each toolbox, there will be one table. The table name corresponds to the name of the toolbox.