Enterprise geodatabase size and name limits
Limits on the size of database objects in an enterprise geodatabase are mostly dependent on hardware limitations. Limits on database object name sizes is the smaller of either the limit enforced by the database management system (DBMS) or geodatabase limit. Limits vary from DBMS to DBMS. The types of characters allowed in object names vary by DBMS but are also affected by how ArcGIS stores and queries the object information.
Size limits
Most size limits in a database depend on the DBMS edition and hardware limitations. One exception is the number of fields (columns) supported in a table or feature class; the maximum number is 500. Be aware, though, that depending on the data types, the maximum number of columns in a table could be less than 500. Most database vendors do not recommend creating tables with over 200 columns of any data type.
Number of characters in object names
The number of characters listed assumes the use of ANSI text. UTF-8 characters use at least twice as many bytes as ANSI characters, thereby reducing the number of allowed characters.
DB2 | Informix | Oracle | PostgreSQL | SQL Server | |
|---|---|---|---|---|---|
Database name | 8 | 31 | 30 | 31 | 31 |
Field (column) name | 31 | 31 | 30 | 31 | 31 |
Index name | 128 | 128 | 30 | 63 | 128 |
Password | 31 | 31 | 31 | 31 | 31 |
Table or feature class alias | 31 | 31 | 30 | 31 | 31 |
Table or feature class name | 128 | 128 | 30 | 63 | 128 |
User name | 30 | 31 | 30 | 31 | 31 |
Version name | 62 | 62 | 62 | 62 | 62 |
Versioned view name | 128 | 128 | 30 | 63 | 128 |
View name | 128 | 128 | 30 | 63 | 128 |
Character type limits in object names
Database management systems have different definitions of acceptable characters for object names. Most must begin with a letter and cannot contain spaces, back slashes, or reserved DBMS keywords. Some allow special characters such as forward slashes (/), underscores (_), dollar signs ($), dashes (-), dots (.), or mixed cases. Sometimes the DBMS allows you to use special characters, reserved keywords, or force mixed, upper-, or lowercase names if you provide the object name enclosed in delimiters, such as double quotation marks.
However, ArcGIS does not delimit object names. Do not create any tables, feature classes, databases, users*, roles, or other object names that require delimiters if you will be using it with ArcGIS. The object will be created in the database, but you cannot access it from ArcGIS.
*SQL Server user names containing special characters are delimited to fully support Active Directory Groups and Windows Authenticated logins.