Spatial data types store the spatial attributes that allow you to visualize data on a map. Many databases automatically include spatial data types. Others require some configuration or an installation to use a spatial data type. The following sections list all the databases ArcGIS supports, what spatial data types are supported in each, and what, if any, configuration is needed to use a spatial data type in each database.
ALTIBASE comes with a spatial type: Geometry. To use this spatial type, you must create two system tables in ALTIBASE.
Dameng includes its own ST_Geometry spatial type; however, you must initialize it.
Db2 databases include their own ST_Geometry spatial type. No configuration is needed to use it.
IBM Netezza Data Warehouse Appliance
Netezza offers two packages to store spatial data: the legacy Netezza Spatial Package and the Netezza Spatial Esri Package.
If you use the legacy Netezza Spatial Package, ArcGIS requires that the spatial column in the table be named shape. If the name of the column is not shape, create a view on the table and set the alias of the spatial column to shape.
Note that the spatial package you use affects how you configure the Netezza ODBC driver to connect to Netezza from client applications.
Microsoft SQL Server and Microsoft Azure SQL Database
Both SQL Server and Microsoft Azure SQL Database include two spatial types: Geometry and Geography. You do not have to install or configure these spatial types, as they are present automatically.
ArcGIS supports two spatial types in Oracle: ST_Geometry and SDO_Geometry.
If you will define queries that perform spatial functions on your layers, you also need to configure the Oracle extproc to use ST_Geometry.
Oracle Locator objects, including the SDO_Geometry type, are present by default in Oracle databases. Therefore, you can access the SDO_Geometry type without additional installations, but to access all SDO_Geometry functions, you may need to install Oracle Spatial in the database.
ArcGIS supports three spatial types in PostgreSQL: ST_Geometry, PostGIS geometry, and PostGIS geography. Install one or all of these types in your database.
To install the ST_Geometry type, place the st_geometry library in your PostgreSQL installation's lib directory. Next, use the Create Spatial Type geoprocessing tool to create the ST_Geometry type in the database. See Add the ST_Geometry type to a PostgreSQL database for instructions.
PostGIS is a third-party, open source installation. To use the PostGIS geometry or geography type, install PostGIS on the PostgreSQL database cluster. Once installed, either use the PostGIS template database to create a database containing the PostGIS types, or configure an existing database to use the PostGIS types. See PostGIS documentation for information on the installation and configuration of PostGIS.
Spatial data is stored in the SAP HANA ST_Geometry type, which is included in the default SAP HANA data warehouse installation.
To store spatial data in a SQLite database, you can either install SpatiaLite, add the ST_Geometry type to the database, or create a GeoPackage. See Spatially enable an SQLite database for more information and instructions.
Alternatively, you can use the Create SQLite Database geoprocessing tool to create a GeoPackage or SQLite database that uses ST_Geometry or SpatiaLite storage.
Teradata Data Warehouse Appliance
Teradata includes a spatial data type; no configuration is needed to use it. Be aware, however, that ArcGIS requires that the spatial column in a Teradata feature class be named shape. If the name of the column is not shape, create a view on the table and set the alias of the spatial column to shape.