SQL Server connection

pierrel_22199
pierrel_22199 New Altair Community Member
edited September 27 in Community Q&A

Hi ,

Altair SLC is running on a server where SAS9.4  is installed. SAS Access To  SQL SERVER is under  licence  at my site.  SAS Access to Server is in fact   using on Linux an ODBC connection, SAS provides its customers  with a Data Direct Acces ODBC driver.

After numerous efforts , I was able  to define the LD_LABRARY_PATH for my SLC session on the Linux Server.

 Contents of the environment  variable : /tools/list/oracle/product/client64/19.8.0/lib:/app/list/data/sasbin/AccessClients/9.4/SQLServer/lib:/app/list/data/altairbin/altairslc-5.24.2.0.1334-ga-release/bin

  When trying  to connect a SQL Server database , I get the following error 

169       ODS HTML(ID=WBHTML) BODY=WPSWBHTM GPATH="/app/list/data/saswork/altairwork/WPS_work964
169     ! 20012e9fa_lr087app10007";
ERROR: A database error occurred. The database specific error follows:
       DB: :
170       LIBNAME CAMARSQL SQLSVR  Datasrc=CAMARE7  SCHEMA=dbo  USER=capilmaj01  PASSWORD=XXXXXX
170     ! X ;
ERROR: Could not connect to DB
171       quit; run;

I am able to access this SQL Server database with SAS Enterprise Guide.

Is what I'am trying to perform possible ? What should I check eventually ?

Any clue welcome.

 

 

 

Tagged:

Answers

  • Nico Chart_21517
    Nico Chart_21517
    Altair Employee
    edited September 27

    Hi,

    If you are entitled to Altair customer support then we would like create a ticket in our support system so that we can carefully work on this issue and provide a good solution for you. Would you mind sharing your details - or just email us at dasupport@altair.com.

    We don't have any knowledge or information about "SAS9.4" so we will have to reply based on our knowledge of our own Altair SLC product. Altair SLC does not bundle a "Data Direct Acces ODBC driver" with our software but we are certainly compatible with Microsoft's own unixODBC driver for SQLServer and I would guess that the Data Direct driver will probably work too.

    Have you used the unixODBC 'isql' utility to check the connection from the SLC machine to the database? This can be a useful check. And if you can share the relevant sections of your odbc.ini and odbcinst.ini files that might help us spot any potential issues.

    Best Regards,
    Nico

Categories