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; } } }

Arcgis Pro 2.5 - SQL Database Connection

RickeyFight

So I just opened an old (pre 2.5) pro project and noticed that after the update data from a database connection would not load. I thought this was strange so I opened an brand new project and I get this error when trying to add a SQL database. My SQL Server Client software is updated.

Any ideas about how to to fix this?

Find more posts tagged with

Accepted answers

Map2021

Yes this solved our connection issue.

Here is the link to the Driver we installed.

Download Microsoft® ODBC Driver 17 for SQL Server® - Windows, Linux, & macOS from Official Microsoft Download Center

All comments

KoryKramer

FWIW on this thread, as far as we can tell, we think this occurs when a machine only has the SQL Server 2012 Native Client installed. Note that that client has not been supported since ArcGIS Pro 2.2. While it may have continued to work throughout Pro 2.3 and 2.4, it was not supported (see Microsoft SQL Server database requirements for ArcGIS 10.7.x and ArcGIS Pro 2.3 and 2.4—System Requirements | Documentat… ). As stated on this thread, for one user, updating to ODBC driver 11 resolved the issue for SQL Server 2012 but more importantly, as also noted above, be sure to check the requirements for ArcGIS Pro 2.5 here: Microsoft SQL Server database requirements for ArcGIS 10.8 and ArcGIS Pro 2.5—System Requirements | Documentation to ensure you are running a supported version of SQL Server along with a compatible driver.

I'm sharing this in the hope that it helps to clarify the situation based on the information we have. At this point, we have no indication that ArcGIS Pro 2.5 "breaks" database connections when running a supported version and compatible driver.

Thank you!

KeithMiller3

I've found that installing the ODBC driver does work, but is MUCH slower than the native SQL driver used to be.

Anonymous User

2.5 broke my 2012 sql connections as well, but after reading this blog I decided to try Driver 11:

ODBC Driver 11 worked for me with SQL server (express) 2012 🙂

George Thompson

I would recommend having it upgraded to a supported SQL Server version; Microsoft SQL Server database requirements for ArcGIS 10.7.x and ArcGIS Pro 2.3 and 2.4—System Requirements | Documentat…

It "may" connect and act like normal but then may also not work.

JulieDel_Muto

What if your database is still on SQL 2012?

Brady

Same here. The driver updated fixed it. Thanks muchly

KimberlyGraham1

I had the same issue, the driver download fixed it. Thanks, Kory!

Map2021

Yes this solved our connection issue.

Here is the link to the Driver we installed.

Download Microsoft® ODBC Driver 17 for SQL Server® - Windows, Linux, & macOS from Official Microsoft Download Center

KoryKramer

Check the odbc driver...

KoryKramer

Yes, that documentation will be opening up soon with the release of 10.8...

ThomasColson

Your quickest solution is going to be call Tech Support, but, if you could share (which they will also ask for)

What Vendor and Version of DB? What OS is it on? You say client is up to date, what version of client and when installed? Can you connect to the DB using other apps on same workstation (SSMS?)

Kory Kramer‌ will Microsoft SQL Server database requirements for ArcGIS 10.7.x and ArcGIS Pro 2.3 and 2.4—System Requirements | Documentat… be updated with 2.5 requirements?

George Thompson

I Just tested with ArcGIS Pro 2.5 and SQL Server 2017 and had no issues. I just upgraded from 2.4.3 yesterday. I was able to connect to all my geodatabases and non-geodatabases. I also tried OS and DB authentication with no issues.

What is the version of SQL Server being used?

Another option may be to reinstall the SQL Server Native client. I am not sure how the update would impact that but worth a try.

MatthewSkewes2

Yeah similar issues here connecting to SQL Server, hopefully it's an easy fix otherwise I'll have to roll back.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

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