Hi, we are trying to connect to SQL Server database to load the existing data. We've tried updating the Pro and installing the latest patch. Uninstalled and installed the ODBC Driver for SQL Server, but it seems that the connection is still loading and is not pushing through. We are using ArcGIS Pro 3.2.2 and SQL Server 2017. Enterprise setup was installed in Linux OS, but Pro is installed in Windows. Has anyone experienced the same problem? What can we do about this? Thank you in advance.
Just so I am clear, you cannot connect with ArcGIS Pro to SQL Server at all. Is there any error message, if so please provide?
Are you using the Microsoft ODBC Driver 17 for SQL Server?
Is SQL Server installed on Linux or Windows O/S?
You mention Enterprise, but need clarification on this.
Is there all ready an enterprise geodatabase or just a SQL database on that instance?
Hi, George! There is no error appearing when we try to connect to SQL Server, just the loading line. We have installed MS ODBC Driver 17. SQL is installed in Linux. I just mentioned the Enterprise part because I'm not sure if it will help. We're trying to connect first to the database from SQL Server to access data.
There is an update to our problem though. It appears that the system tables that come with the back up file was corrupted. My colleague deleted those corrupted tables and it finally connected.
If you create a new enterprise geodatabase (or database) are you able to connect to it and load / view data?
If you deleted the system tables, that could cause additional issues.
Hi, George. We'll try creating a new enterprise gdb and we'll load the data there. We'll check if this works. Thank you!
Another concern of ours was the client sent a .bak file of the data and from what we know, we have to restore this first in the same DB which was SQL Server. We restored this in SQL and we are now trying to connect to that same DB in Pro.
After you restore the backup to SQL Server, you must create the users to match what is in the restored database. Once the users are in the SQL instance you must re-sync the logins from the database to the instance: https://support.esri.com/en-us/knowledge-base/re-synch-sql-server-logins-or-users-after-restoring-a-...
That should allow you to connect as those users. If the restored database is all DBO, then a DBO users on the new instance should be able to connect.
Hi, George! Update. We tried creating an EGDB and loading/restoring the data there but it failed.
We'll try restoring it again on SQL Server and create users to match what is in the restored DB.