Supported databases

Insights in ArcGIS Online
Insights in ArcGIS Enterprise
Insights desktop
Note:

Database connections are supported in Insights in ArcGIS Enterprise and Insights desktop.

Database connections allow you to connect directly with your database tables in Insights. The tables below list the supported databases and versions you can connect to when using Insights.

Google BigQuery

BigQuery is a cloud-based database that updates automatically. BigQuery is supported in the following versions of Insights:

Insights 2021.2Insights 2021.1Insights 2020.3Insights 2020.2Insights 3.4

Supported*

Not supported

*Spatial capabilities are not supported at Insights 2021.1. Spatial capabilities are in preview at Insights 2021.2.

Note:

Insights uses service account authentication when connecting BigQuery. A service account with an Editor, Owner, or Viewer role is required to create a connection from Insights to BigQuery. For more information, see Create a service account and private key in the Insights connector guide.

Limitations

String fields in tables from BigQuery connections cannot be converted to date/time fields from the data pane or using a DATEVALUE calculation that does not specify a date format. Date and time data should be stored in the database using a valid date or time data type or calculated using an expression that includes a valid date format.

BigQuery uses approximate calculations for median and percentile. Therefore, median and percentile statistics calculated on datasets from BigQuery may not match the results seen from other data sources. Median and percentile statistics are available on summary tables and some charts.

Note:

The median value on a box plot represents the true median, rather than the approximate median calculated by BigQuery.

The following spatial capabilities are not currently supported for BigQuery:

  • Use Spatial Aggregation with lines or areas in the Choose a layer to summarize parameter.
  • Use Enable location with geography or address.
  • Use Enable location with coordinates for any spatial reference other than 4326 (World Geodetic System 1984).
  • Use Buffer/Drive Times.
  • Use Calculate Density.
  • Use Calculate Density Ratio.
  • Use K-Means Clusters.
  • Use Spatial Mean.
  • Use Enrich Data.

Microsoft SQL Server

The following table lists the supported versions of Microsoft SQL Server:

Insights 2021.2Insights 2021.1Insights 2020.3Insights 2020.2Insights 3.4

Standard/Enterprise editions:

  • Microsoft SQL Server 2019 (64 bit)
  • Microsoft SQL Server 2019 for Linux (64 bit)
  • Microsoft SQL Server 2017 (64 bit)
  • Microsoft SQL Server 2017 for Linux (64 bit)
  • Microsoft SQL Server 2016 (64 bit)
  • Microsoft SQL Server 2014 (64 bit)

Standard/Enterprise editions:

  • Microsoft SQL Server 2017 (64 bit)
  • Microsoft SQL Server 2017 for Linux (64 bit)
  • Microsoft SQL Server 2016 (64 bit)
  • Microsoft SQL Server 2014 (64 bit)

Express edition:

  • Microsoft SQL Server 2017 (64 bit)

Cloud database as a service:

  • Microsoft Azure SQL Database

Oracle

The following table lists the supported versions of Oracle:

Insights 2021.2Insights 2021.1Insights 2020.3Insights 2020.2Insights 3.4

Standard/Standard One/Enterprise editions:

  • Oracle 19c (64 bit)
  • Oracle 18c (64 bit)
  • Oracle 12c R2 (64 bit) 12.2.0.1
  • Oracle 12c R1 (64 bit) 12.1.0.2
  • Oracle 11g R2 (64 bit) 11.2.0.4

Standard/Standard One/Enterprise editions:

  • Oracle 18c (64 bit)
  • Oracle 12c R2 (64 bit) 12.2.0.1
  • Oracle 12c R1 (64 bit) 12.1.0.2
  • Oracle 11g R2 (64 bit) 11.2.0.4
Note:

Oracle 11g supports read-only functionality. Other Oracle database versions support read/write functionality.

Advanced string matching

Advanced string matching logic uses case-insensitive string comparisons and matches null and empty strings. The logic improves outputs for joins on string fields, filters on string fields, and field calculations using equal to (=) or not equal to (<>) on string fields, but negatively affects database performance.

Advanced string matching functionality in Oracle databases is used in Insights 2020.3 and earlier but has been deprecated for Insights 2021.1 and higher. Connections created in Insights 2020.3 and earlier will continue to use advanced string matching unless the property is changed manually.

An ArcGIS administrator can manually override the advancedStringMatching property for the RelationalCatalogServer in the ArcGIS Server Administrator Directory.

PostgreSQL

The following table lists the supported versions of PostgreSQL:

Insights 2021.2Insights 2021.1Insights 2020.3Insights 2020.2Insights 3.4

Postgres PostGIS support:

  • PostgreSQL 13 (64 bit) with PostGIS 3.03
  • PostgreSQL 11 (64 bit) with PostGIS 2.5
  • PostgreSQL 10 (64 bit) with PostGIS 2.4 or 2.5
  • PostgreSQL 9.6 (64 bit) with PostGIS 2.3, 2.4, or 2.5

Postgres PostGIS support:

  • PostgreSQL 11 (64 bit) with PostGIS 2.5
  • PostgreSQL 10 (64 bit) with PostGIS 2.4 or 2.5
  • PostgreSQL 9.6 (64 bit) with PostGIS 2.3, 2.4, or 2.5

PostgreSQL geodatabase support:

  • PostgreSQL 10.6 (64 bit)
  • PostgreSQL 9.6 (64 bit)
  • PostgreSQL 9.5.12

For PostgreSQL databases without spatial extensions, only versions 9.6, 10, and 11 are supported.

SAP HANA

The following table lists the supported versions of SAP HANA:

Insights 2021.2Insights 2021.1Insights 2020.3Insights 2020.2Insights 3.4
  • SAP HANA Cloud
  • SAP HANA 2.0 SPS05
  • SAP HANA 2.0 SPS04
  • SAP HANA 2.0 SPS04
  • SAP HANA 2.0 SPS03
  • SAP HANA 2.0 SPS02
  • SAP HANA 1.0 SPS12
  • SAP HANA 2.0 SPS03
  • SAP HANA 2.0 SPS02
  • SAP HANA 1.0 SPS12
Note:

SAP HANA modeling views are not supported.

Snowflake

Snowflake is a cloud-based database that updates automatically. Snowflake is supported in the following versions of Insights:

Insights 2021.2Insights 2021.1Insights 2020.3Insights 2020.2Insights 3.4

Supported

Not supported

*Spatial capabilities are not supported at Insights 2021.1. Spatial capabilities are in preview at Insights 2021.2.

Limitations

String fields in tables from Snowflake connections cannot be converted to date/time fields from the data pane or using a DATEVALUE calculation that does not specify a date format. Date and time data should be stored in the database using a valid date or time data type or calculated using an expression that includes a valid date format.

The following spatial capabilities are not currently supported for Snowflake:

  • Use Spatial Aggregation with lines or areas in the Choose a layer to summarize parameter.
  • Use Enable location with geography or address.
  • Use Enable location with coordinates for any spatial reference other than 4326 (World Geodetic System 1984).
  • Use Buffer/Drive Times.
  • Use Calculate Density.
  • Use Calculate Density Ratio.
  • Use K-Means Clusters.
  • Use Spatial Mean.
  • Use Enrich Data.

Enterprise geodatabases

Insights in ArcGIS Enterprise and Insights desktop allow you to create a connection to a supported Microsoft SQL Server, Oracle, SAP HANA, or PostgreSQL database that has a non-versioned enterprise geodatabase defined. If the geodatabase is versioned, the data must be unregistered as versioned to work in Insights. Currently, only geodatabase user tables not created under the sde user schema can be viewed and accessed from Insights. Insights does not work directly with file and personal geodatabases.

Additional database platforms

Note:

This functionality is currently in Preview.

In addition to the supported databases, connectors can also be added for other relational databases that use a Java Database Connectivity (JDBC) driver. See the Insights connector guide for more information about the required configuration files and connectors that have been certified in Insights.

Additional database connectors are available in the following Insights versions:

Insights 2021.2Insights 2021.1Insights 2020.3Insights 2020.2Insights 3.4

Preview

Not supported

Limitations

String fields cannot be converted to date/time fields from the data pane or using a DATEVALUE calculation that does not specify a date format for these connectors. Date and time data should be stored in the database using a valid date or time data type (configured in the dialect.yml file) or calculated using an expression that includes a valid date format. See the Insights connector guide for more information on configuring data types.

The following spatial capabilities are not currently supported:

  • Use Spatial Aggregation with lines or areas in the Choose a layer to summarize parameter.
  • Use Enable location with geography or address.
  • Use Enable location with coordinates for any spatial reference other than 4326 (World Geodetic System 1984).
  • Use Buffer/Drive Times.
  • Use Calculate Density.
  • Use Calculate Density Ratio.
  • Use K-Means Clusters.
  • Use Spatial Mean.
  • Use Enrich Data.

Resources

For more information about databases, see the following:

Next steps

Now that you know which databases are supported, the next step is to download the required vendor files for your database type. For more information, see Required vendor files.