ArcGIS Pro 2.2.4 SQL Server Compatibility

481
4
04-02-2019 01:30 PM
Highlighted
New Contributor III

Does anyone know the SQL Server version compatibility for Pro 2.2.4?

We are seeing odd behavior inside of Pro when working with Enterprise GDB feature classes that are joined to other tables.  When we select the joined features in the map they are not highlighted and when we open the table after selecting features, we receive an error that the table does not have an OID. 

The same workflow can be done inside of ArcMap no problem.

We are on MSSQL Server 2012 SP3 and have been holding off on upgrading to Pro 2.3 because it requires at least SQL Server 2014 and we are in the process of upgrading.

Any insight would be helpful.

Thank you,

Brian

Reply
0 Kudos
4 Replies
Highlighted
Esri Frequent Contributor

Geodatabase

--- George T.
Reply
0 Kudos
Highlighted
MVP Frequent Contributor

Unfortunately, ESRI decided to upgrade the Pro Online Help to only show the latest version, the day it's released, so https://desktop.arcgis.com/en/system-requirements/latest/database-requirements-sqlserver.htm# doesn't appear to be helpful in your case. However, from the 2.2 Installed Help:

Microsoft SQL Server database requirements for ArcGIS Pro 2.2

Microsoft SQL Server database requirements for ArcGIS Pro 2.2

Visit Esri Support for general support information on Esri's Supported Environment Policy.

Supported database versions

Enterprise/Standard/Developer* 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)

Microsoft SQL Server 2012 SP3 (64-bit)

Express editions

Microsoft SQL Server 2017 (64-bit)

Microsoft SQL Server 2016 (64-bit)

Microsoft SQL Server 2014 (64-bit)

Microsoft SQL Server 2012 SP3 (64-bit)

Suggests that you're legit with 2012 SP3, so a call to Tech Support is the path forward here. 

Highlighted
Esri Notable Contributor
Highlighted
New Contributor III

I discovered what was causing our issue.

We were joining an enterprise geodatabase feature class to a SQL table from our accounting database. The table from our accounting database is not an SDE registered table, so it does not have an OBJECTID field.  In ArcMap, this was not a problem since the feature class/shapefile has the required OID field.  Pro, however, does not function in the same manner.

In Pro, you are required to add the non-SDE registered table to your project, at which point you are prompted to choose a field in that table that is a unique identifier.  Pro then adds the table to the project and creates a temporary OID field.  At this point, you can then join your feature class/shapefile to the table.

Alternatively, we were able to create a database view between the feature class/accounting table and were able to work with that without issue.

Thanks,

Brian

Reply
0 Kudos