Enterprise geodatabase size and name limits

Limits on the size of database objects in an enterprise geodatabase are mostly dependent on hardware limitations. The limit on database object name size is the smaller of either the limit enforced by the database management system or the geodatabase limit. Limits vary from one database management system to the next. The types of characters allowed in object names vary by database management system but are also affected by how ArcGIS stores and queries the object information.

Size limits

Most size limits in a database depend on the database management system edition and hardware limitations. See the documentation for your database management system to determine size limits.

Number of characters in object names

The following table lists the maximum number of characters allowed by ArcGIS for each type of object name:

Object typeMaximum bytes allowed by ArcGIS

Database name

Up to the database management system's limit.

Table, feature class, view, or index name

Up to the database management system's limit.

Field (column) name

Up to the database management system's limit.

Password

256 when reading passwords, 75 when creating passwords

User or role name

Up to the database management system's limit.

Character type limits in object names

Database management systems have different definitions of acceptable characters for object names. Most allow you to use unacceptable characters if you provide the object name enclosed in delimiters, such as double quotation marks.

However, ArcGIS does not add delimiters when querying objects in the database. Do not create any tables, feature classes, indexes, databases, users, roles, or other object names that require delimiters if you will use them in ArcGIS. The object will be created in the database, but you cannot access it from ArcGIS.

Similarly, delimiters are not added when you create database objects, such as a table or database, from ArcGIS. If the name you provide when you create the object uses character casing that the database does not support unless the text is inside delimiters, the underlying database changes the casing. The next time you attempt to access the object from ArcGIS, you may receive an error message indicating that the object does not exist.

Number of characters in nonobject names

Enterprise geodatabase functionality provides constructs that appear to be database objects when viewed in ArcGIS Pro but are actually values in geodatabase system tables. The names of these constructs also have character limits. Examples of these are listed in the table below.

Geodatabase construct typeMaximum bytes allowed

Domain name

257

Feature dataset name

159

Field alias

255

Version name

62