nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

SQL Server 2016 Compatibility with ArcGIS Enterprise 11.3

CharliePoate

While we wait for our IT department to upgrade our instance of SQL Server from 2016 we are tempted to test upgrading ArcGIS Enterprise from 11.1 to 11.3. Has anyone tried this, appreciating the fact that Esri state they do not support SQL Server 2016 with 11.3?

Trouver plus de publications taguées avec

Accepted answers

All comments

DavidColey

I wouldn't try it. You might be able to get away with it, but it could be very unstable. I do know that with Pro 3.3 and Enterprise 11.3 you cannot register a 2016 sql sde database as a database with Portal.

If you have a distributed deployment, you could update Portal, the hosting site server, and the relational datastore to 11.3 while a federated server site remains at 11.1. This is assuming that any sde sql datastore is registered with the federated Server site only, and not with Enterprise (does not appear as a registered data connection item in your Portal content).

CharliePoate

Thanks for the response. I was thinking the Pro connection could be a problem. We have a multi-box deployment so exploring your other suggestion might be something we will look into.

ryanuthoff

I've tested an already existing 2016 EGDB with ArcGIS Pro 3.3 and I was able to connect to it, but I wouldn't recommend it since it's not officially supported.

CalvinHarmin

Does anyone know why SQL Server 2016 is no longer supported? They list the SQL Server 2017 supported driver being the same ODBC SQL Server 17 driver that we use for our SQL Server 2016 instance currently. I'm not going to pretend like I know much about what's happening behind the curtain regarding RDBMS programming and functionalities that would lead a version to be supported or not, but I'm very curious if there's a straightforward answer.

I think my org will not be willing to update our SQL Server version above 2016 for 1 to 2 years at least for various reasons, unless there is a fire under our butts for some other reason besides Enterprise 11.3. I may have to set up a Postgres instance on a new machine just for my Enterprise Geodatabases instead in order to move forward with 11.3.

CalvinHarmin

Update: I got a response from an ESRI engineer:

Microsoft’s mainstream support of SQL Server 2016 ended in July 2021, and extended support ends in July 2026. Because Enterprise 11.3 is supported well beyond that date, we could not offer support for SQL Server 2016 with ArcGIS Enterprise 11.3.

And a separate response from an ESRI support rep:

Please refer to the screenshot that I got from this link as attached below:-

Just to let you know, the 'older ArcGIS clients' referred to in the picture are pointing to all old versions of software configured with ArcGIS Enterprise. This includes the SQL Server version as well and is not limited to the DBMS version.

As stated in the picture, you still can perform a normal task within the ArcGIS Enterprise and Pro, and as stated in my previous email, the connectivity between your Pro and ArcGIS Enterprise to the SQL Server will not be affected.

However, if you open any datasets that need a compatible version of the SQL Server, then only you will observe an error message as stated in the screenshot. Aside from that, I don't think it will give an issue to your deployment.

JeffLegato1

If I read this correctly (and from some personal experience), it is possible to upgrade, but DO NOT implement any new GDB functionality until your SQL Server is upgraded to at least version 17 when using PRO 3.3. We just recently upgraded to 11.1 and then 11.3 but our SQL Server is at 16. I did notice that if I added a date field (while using PRO 3.3) using the new 'date only' field type it threw an incompatible version error when I tried publishing a service. I had to delete the field. This happened at 11.1/PRO3.3. Had I known about this we probably would have held off on our upgrade until after the SQL server upgrade but here we are. We are now planning the SQL upgrade sooner rather than later but that will impact several other systems here.

Which brings me to a complaint. We probably should have held off on upgrading ArcGIS PRO but you get that upgrade nag every time you launch and there's no link there for information as to what will break once you upgrade PRO. I'm learning now how integrated Enterprise and PRO are. They really go hand in hand. We will be much more careful going forward in the future with upgrading ArcGIS PRO in conjunction with Enterprise.

ryanuthoff

I know this doesn't really help you now since you already upgraded, but for future reference, you can disable the ArcGIS Pro update notifications.

https://support.esri.com/en-us/knowledge-base/is-it-possible-to-block-update-notifications-in-arcgis--000012486

Edit: There are two different methods of disabling updates. Here is a second way: https://pro.arcgis.com/en/pro-app/latest/get-started/update-arcgis-pro.htm

We also found out the hard way how integrated Enterprise and Pro are. I think I read somewhere that it's best practice for Pro and Enterprise to stay within two versions of each other, but even a one version difference has caused us issues. Going forward, I think it's best practice to always keep Pro and Enterprise at the same version, and upgrade everything together.

Rejoindre la conversation

Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.

Liens rapides

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.