SAS Library Connection for Azure Database

[jcromwell77]

LIBNAME pubtest ODBC  DATAsrc=TEST_DB  
SCHEMA=dbo  ;

LIBNAME pubprod ODBC  DATAsrc=PROD_DB  
SCHEMA=dbo  ;

I have two connections: test A and prod A.  When I use test A I get a good connection, and I'm able to run a PROC SQL query with results.  However, when I run prod A, I get a good connection, but I get a "Error: File PUBPROD.<data table>.Data does not exist."  I've looked at the configuration for each in Management Console, and I cannot find a difference.  I've also compared these against another test (B) and prod (B) connection (both of these work).

The only difference between the prod A  and the other 3 connections (test A, test B, & prod B) is it is brand new (just created last week).  The other 3 were created some time ago before I started, and the creator is no longer with the org.

Is this an issue in the SAS Management Console Administration, the Windows Server Administration (where the SAS server lives), or elsewhere?  I'm quite new to SAS administration, and I've not found a good answer anywhere else.

Thanks.

[MarcoGhiglieriO]

I don't think this is a SAS related problem.

The "Error: File PUBPROD.<data table>.Data does not exist." suggests that the ODBC DSN is connecting, but there's not that table.

Did you check the table existence via another ODBC client?

[jcromwell77]

The connection for all of the tables is in an Azure DB, and the tables do exist in Azure.  I verified the tables via SSMS, so I know they're good.

The DSN Drivers on the Windows side are set to ODBC Driver 17 for SQL Server for Test A and Prod A, and SQL Server for Test B and Prod B.  Don't know if this makes a difference or not.  We originally tried SQL Server for Prod A, but switched it.

[jcromwell77 · Accepted solution]

The issue has been resolved:

The Default database in the DSN was set to master instead of the PROD_DB.  Once this was changed, I was able to connect to the table.