Skip To Content

DBMS data types supported in ArcGIS

When you create a table or add a column to a table in a database, you define a specific data type for the column. Data types determine the following:

  • What values you can store in the column
  • What operations you can use on the data in that column
  • How the data in that column is stored in the database

ArcGIS works with specific data types. When you access a database table through a Database Connection, query layer, or web service, ArcGIS filters out any unsupported data types. ArcGIS does not display unsupported data types, and you cannot edit unsupported data types through ArcGIS. Similarly, when you use ArcGIS to copy and paste tables containing unsupported data types from one database to another, ArcGIS only pastes columns that use a supported data type.

The first column in the following table lists the ArcGIS data types. The second column lists the database management system data type that ArcGIS creates. The third column shows what other database management system data types (if any) map to the ArcGIS data type when you view a table that you created outside ArcGIS. The last column provides additional information when needed.

ALTIBASE

ArcGIS data typesALTIBASE data types createdOther ALTIBASE data types that can be viewedNotes

BLOB

BLOB

DATE

Date

DOUBLE

Numeric(p,s)

By default, p (precision) = 38 and s (scale) = 8.

FLOAT

Numeric(p,s)

By default, p (precision) = 38 and s (scale) = 8.

GEOMETRY

Geometry

GUID

Fixed-length character(38)

LONG INTEGER

Integer

OBJECT ID

Integer

SHORT INTEGER

Smallint

TEXT

Variable length nvarchar(p)

P is the field length you specify for the TEXT field. The default value is 50.

Dameng

ArcGIS data types Dameng data types createdOther Dameng data types that can be viewedNotes

BLOB

BLOB

DATE

Datetime6

DOUBLE

Dec(p,s)

By default, p (precision) = 38 and s (scale) = 8.

FLOAT

Dec(p,s)

By default, p (precision) = 38 and s (scale) = 8.

GEOMETRY

ST_Geometry

GUID

Char(38)

LONG INTEGER

Integer

OBJECT ID

Integer

SHORT INTEGER

Smallint

TEXT

Varchar

P is the field length you specify for the TEXT field. The default value is 50.

IBM Db2

ArcGIS data typesDb2 data types createdOther Db2 data types that can be viewedNotes

BLOB

BLOB

DATE

TIMESTAMP

DOUBLE

DECIMAL(p,s)

The precision and scale specified in ArcGIS can affect the resultant data type created in the database. See ArcGIS field data types for more information.

FLOAT

DECIMAL(p,s)

The precision and scale specified in ArcGIS can affect the resultant data type created in the database. See ArcGIS field data types for more information.

GEOMETRY

ST_GEOMETRY

GLOBAL ID

CHAR(38)

Only supported in geodatabases.

GUID

CHAR(UUID LEN)

LONG INTEGER

INTEGER

OBJECT ID

CHARACTER(38) when created in enterprise geodatabases

INTEGER with IDENTITY property when created in a database

The ArcGIS type ObjectID is the registered row ID column for the table (or feature class.) Only one may exist per table.

RASTER

BLOB

Only supported in geodatabases.

SHORT INTEGER

SMALLINT

TEXT

VARCHAR

CHAR

Microsoft Azure SQL Database

ArcGIS data typesAzure SQL Database data types createdOther Azure SQL Database data types that can be viewedNotes

BLOB

VARBINARY(MAX)

BINARY, IMAGE, TIMESTAMP, VARBINARY(n)

DATE

DATETIME2(7)

DATETIME2(n), DATETIME, SMALLDATETIME

DOUBLE

NUMERIC(p,s)

DECIMAL, FLOAT, MONEY, SMALLMONEY

The precision and scale specified in ArcGIS can affect the resultant data type created in the database.

FLOAT

NUMERIC(p,s)

REAL

The precision and scale specified in ArcGIS can affect the resultant data type created in the database.

GEOMETRY

GEOMETRY

GEOGRAPHY

ArcGIS does not support the following GEOMETRY subtypes:

  • CircularString
  • CompoundCurve
  • CurvePolygon
  • GeometryCollection

GUID

UNIQUEIDENTIFIER

LONG INTEGER

INT

OBJECTID

INTEGER

Only one may exist per table

SHORT INTEGER

SMALLINT

BIT, TINYINT

TEXT

VARCHAR, NVARCHAR, VARCHAR(MAX), NVARCHAR(MAX)

CHAR, NCHAR

Microsoft SQL Server

ArcGIS data typesSQL Server data types createdOther SQL Server data types that can be viewedNotes

BLOB

VARBINARY(MAX)

BINARY, IMAGE, TIMESTAMP, VARBINARY(n)

DATE

DATETIME2(7)

DATETIME2(n), DATETIME, SMALLDATETIME

DOUBLE

NUMERIC(p,s)

DECIMAL, FLOAT, MONEY, SMALLMONEY

The precision and scale specified in ArcGIS can affect the resultant data type created in the database. See ArcGIS field data types for more information.

FLOAT

NUMERIC(p,s)

REAL

The precision and scale specified in ArcGIS can affect the resultant data type created in the database. See ArcGIS field data types for more information.

GEOMETRY

  • GEOMETRY
  • GEOGRAPHY

Specify whether to use GEOMETRY or GEOGRAPHY when a feature class is created.

ArcGIS does not support the following GEOMETRY subtypes:

  • CircularString
  • CompoundCurve
  • CurvePolygon
  • GeometryCollection

GLOBAL ID

UNIQUEIDENTIFIER

Only supported in geodatabases.

GUID

UNIQUEIDENTIFIER

LONG INTEGER

INT

RASTER

BLOB, INT

Raster data types are only supported in geodatabases.

In enterprise geodatabases, the SQL Server data type that is created depends on the configuration keyword used when you create the raster dataset or mosaic dataset. If the keyword's RASTER_STORAGE parameter is set to RASTERBLOB, a BLOB column is created; if set to BINARY, an INT column is created.

OBJECT ID

INT(4) when created in an enterprise geodatabase

INTEGER with IDENTITY property when created in a database

The ArcGIS type ObjectID is the registered row ID column for the table (or feature class.) Only one may exist per table.

SHORT INTEGER

SMALLINT

BIT, TINYINT

TEXT

VARCHAR, NVARCHAR, VARCHAR(MAX), NVARCHAR(MAX)

CHAR, NCHAR

Netezza Data Warehouse Appliance

ArcGIS data typesNetezza data types createdOther Netezza data types that can be viewedNotes

BLOB

Not supported

DATE

TIMESTAMP

DATE, TIME, TIME WITH TIME ZONE

DOUBLE

NUMERIC(38,8)

BIGINT (alias int8), NUMERIC(p,s), FLOAT(p), REAL, DOUBLE PRECISION

The precision and scale specified in ArcGIS can affect the resultant data type created in the database.

FLOAT

FLOAT(p)

The precision and scale specified in ArcGIS can affect the resultant data type created in the database.

GEOMETRY

VARCHAR(n)

ST_GEOMETRY

If you use the Netezza Spatial Package, a VARCHAR field is created, and you must name the field (or alias it to) shape for ArcGIS to recognize it as a spatial column.

If you use the Netezza Spatial Esri Package, an ST_GEOMETRY field is created. When an ST_GEOMETRY field is used, you are not required to name the field (or alias it to) shape.

GUID

CHAR(38)

LONG INTEGER

INTEGER (alias int or int4)

OBJECTID

INTEGER (alias int or int4)

SHORT INTEGER

SMALLINT (alias int2)

TEXT

NVARCHAR(50)

CHAR(n), NCHAR(n), VARCHAR(n)

If your database is set for Unicode encoding, NVARCHAR will be created. If your database is not set for Unicode encoding, VARCHAR will be created.

Oracle

ArcGIS data typesOracle data types createdOther Oracle data types that can be viewedNotes

BLOB

BLOB

DATE

TIMESTAMP

DATE

DOUBLE

NUMBER(38,8)

NUMBER(p,s)

The precision and scale specified in ArcGIS can affect the resultant data type created in the database. See ArcGIS field data types for more information.

FLOAT

NUMBER(38,8)

NUMBER(p,s)

The precision and scale specified in ArcGIS can affect the resultant data type created in the database. See ArcGIS field data types for more information.

GEOMETRY

ST_GEOMETRY or SDO_GEOMETRY

The Oracle data type that gets created depends on the geometry storage specified when the feature class is created. Oracle Spatial = SDO_GEOMETRY or spatial type = ST_GEOMETRY.

To use ST_Geometry in a database (not geodatabase), you must install it.

GLOBAL ID

CHAR or NCHAR (UUID LEN)

Only supported in geodatabases.

The unique identifier field will be created as NCHAR if the configuration keyword with which you specified the table's creation had the parameter UNICODE_STRING set to TRUE.

GUID

CHAR or NCHAR (UUID LEN)

The unique identifier field will be created as NCHAR in a geodatabase if the configuration keyword with which you specified the table's creation had the parameter UNICODE_STRING set to TRUE.

LONG INTEGER

NUMBER(38)

NUMBER(n)

The value n can be in the range of 5 to 10. If created with ArcGIS Desktop or ArcObjects and precision is set to 0, a NUMBER(38) is created in the database; otherwise, the precision specified is used.

OBJECT ID

NUMBER(38) when created in an enterprise geodatabase

NUMBER(38) with sequence and trigger when created in the following circumstances:

  • You use Oracle 11g.
  • You register an existing Oracle 12c database table with the geodatabase.

NUMBER(38) generated always as identity when you use ArcGIS to create a feature class or table in an Oracle 12c database or use the Add Incrementing ID Field geoprocessing tool to add an ID field to a table in an Oracle 12c database.

The ArcGIS type ObjectID is the registered row ID column for the table (or feature class). Only one can exist per table.

RASTER

RASTERBLOB or BLOB

Rasters are only supported in geodatabases. Which data type is used for the raster field depends on the configuration keyword you specify when you create a mosaic dataset or raster dataset.

SHORT INTEGER

NUMBER(5)

NUMBER(n)

The value n can be in the range of 1 to 5. However, short integer columns can only store values that fall in the range -32,768 to 32,767. Even if the precision on the number is 5, you cannot store a number greater than 32,767 or less than -32,768 in a short integer column.

When created with ArcGIS Desktop, n = 5. This allows you to store short integers that fall within the allowable range.

TEXT

VARCHAR2, CLOB, NVARCHAR2, or NCLOB

PostgreSQL

ArcGIS data typesPostgreSQL data types createdOther PostgreSQL data types that can be viewedNotes

BLOB

BYTEA

DATE

TIMESTAMP WITHOUT ZONE

TIMESTAMP

DOUBLE

NUMERIC(p)

BIG SERIAL, DOUBLE PRECISION

The precision and scale specified in ArcGIS can affect the resultant data type created in the database. See ArcGIS field data types for more information.

FLOAT

NUMERIC(p)

The precision and scale specified in ArcGIS can affect the resultant data type created in the database. See ArcGIS field data types for more information.

GEOMETRY

ST_GEOMETRY, GEOMETRY (PostGIS), GEOGRAPHY (PostGIS)

In a geodatabase, the GEOMETRY_STORAGE setting of the configuration keyword used when creating the feature class determines which data type is created in the database.

To use ST_Geometry in a database (not a geodatabase), you must install it. See Add the ST_Geometry type to a PostgreSQL database for information.

To use the PostGIS geometry or geography type, you must install PostGIS in your PostgreSQL database cluster, and the database itself must be enabled to use PostGIS. See your PostgreSQL documentation for more information.

GLOBAL ID

VARCHAR(38)

Only supported in geodatabases.

GUID

VARCHAR(38)

UUID

LONG INTEGER

INTEGER

SERIAL

OBJECT ID

INTEGER in a geodatabase

SERIAL in a database

The ArcGIS type ObjectID is the registered row ID column for the table (or feature class). Only one can exist per table.

RASTER

BYTEA

Rasters are supported only in geodatabases.

SHORT INTEGER

SMALLINT

REAL

TEXT

CHARACTER VARYING

CHARACTER, VARCHAR, TEXT

SAP HANA

ArcGIS data typesSAP HANA data types createdOther SAP HANA data types that can be viewedNotes

BLOB

BLOB

DATE

timestamp

date, seconddate, time

DOUBLE

decimal(38,8)

decimal(m,n), number(m,n), numeric(m,n), bigint

m > 0

The precision and scale specified in ArcGIS affects the resultant data type created in the database.

FLOAT

decimal(38,8)

decimal(m,n)

m <= 9 and n > 0

The precision and scale specified in ArcGIS affects the resultant data type created in the database.

GEOMETRY

ST_Geometry

GLOBALID

character(38)

GUID

character(38)

Latin character set

LONG INTEGER

integer

decimal(m,0)

m <= 9

OBJECTID

bigint

Only 32-bit numbers stored at this time.

RASTER

Not supported in SAP HANA.

SHORT INTEGER

smallint

tinyint

TEXT

varchar(50)

alphanum(n), nvarchar(n), CLOB, NCLOB

SQLite

SQLite does not implement data types in the same way that most other database management systems do. SQLite has a few storage classes in which you can store different data types. SQLite allows you to name data types, as in the case of the realdate, geometryblob, and uuidtext types that get created in SQLite when you create a date, geometry, or guid field in ArcGIS. It also searches the literal text of the data type for clues as to what data type the column stores. For example, it looks for int and interprets that as an integer field. Therefore, if you specify a data type of point, SQLite sees it is an integer field because point contains the string int.

ArcGIS assumes that the data type specified for the field in the table definition is the data type to be applied to all values in the field. If the data type cannot be recognized by ArcGIS, you will not be able to access the table from ArcGIS.

ArcGIS data typesSQLite data types createdOther SQLite data types that can be viewedNotes

BLOB

blob(n)

DATE

realdate

DOUBLE

float64

numeric, double, float, boolean, real

integer, int, int64, int32 (in databases that do not have SpatiaLite installed)

FLOAT

float64

GEOMETRY

geometryblob

GUID

uuidtext

LONG INTEGER

int32(n)

integer, int, int32 (in databases with SpatiaLite)

integer primary key

n >= -2147483648 and n <= 2147483648

OBJECTID

int32

SHORT INTEGER

int16(n)

n >= -32768 and n<= 32768

TEXT

text(n)

char, varchar, blob

Teradata Data Warehouse Appliance

ArcGIS data typesTeradata data types createdOther Teradata data types that can be viewedNotes

BLOB

blob

Blob created with Teradata default size.

DATE

timestamp

DOUBLE

decimal(38,8)

decimal(n,m), number(n,m), numeric(n,m)

m > 0

The precision and scale specified in ArcGIS can affect the resultant data type created in the database.

FLOAT

decimal(38,8)

decimal(n,m), number(n,m), numeric(n,m)

m > 0

The precision and scale specified in ArcGIS can affect the resultant data type created in the database.

GEOMETRY

CLOB (ST_Geometry)

This field must be named shape for ArcGIS to recognize it as a spatial column.

GUID

character(38) character set latin

LONG INTEGER

integer

decimal(n,m), number(n,m), numeric(n,m)

n = 5, 6, 7, 8, or 9

m = 0

OBJECTID

integer

SHORT INTEGER

smallint

decimal(n,m), number(n,m), numeric(n,m)

n <= 4

m = 0

TEXT

varchar(50) character set unicode

varchar(n) character set unicode, varchar(n) character set latin, char(n) character set unicode, char(n) character set latin, JSON