Help using Base SAS procedures

How to derive my proc sql connection string from libname connection string?

Reply
Super Contributor
Posts: 268

How to derive my proc sql connection string from libname connection string?

Hi guys,

My libname is here - 

 

LIBNAME WWTest ODBC NOPROMPT="server=HMIDWPRD03;driver=sql server;Trusted Connection=yes;Database=WW;" SCHEMA=dbo USER=myid PASSWORD="{sas002}secretalphanumericcode123" ;

 

I tried several kinds of combinations for proc sql but it will not work -

 


23 Proc sql;
24 Connect to odbc ( user=myid password=myunecryptedpwd database="WW.dbo") ;
ERROR: CLI error trying to establish connection: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver
specified

 

I tried datasrc=/ database= /single quote/double quote/ and other combinations but of no avail. 

 

Thanks,

saspert

Super Contributor
Posts: 578

Re: How to derive my proc sql connection string from libname connection string?

Have you tried:

 

connect using WWtest as cWWTest;

 

 

Super Contributor
Posts: 268

Re: How to derive my proc sql connection string from libname connection string?

This is a more OS -related issue as per my supervisor. So we can ignore this for now. Thanks! 

Super User
Posts: 3,101

Re: How to derive my proc sql connection string from libname connection string?

Does your LIBNAME actually work? Supplying a username and password is not required if you are using Windows authentication as your string Trusted Connection=yes; indicates. With this option SQL Server authenticates against your Windows user credentials.

Super Contributor
Posts: 268

Re: How to derive my proc sql connection string from libname connection string?

LIBNAME WW2 ODBC  NOPROMPT="server=ABCDEFGPRD;driver=sql server;Trusted Connection=yes;Database=WW;" ;

 

This works fine. The original library is WW. The new test library I created is WW2. Both are shown as assigned/created.

Super User
Posts: 3,101

Re: How to derive my proc sql connection string from libname connection string?

In that case your same NOPROMPT string should work fine in a CONNECTION statement.

Ask a Question
Discussion stats
  • 5 replies
  • 481 views
  • 1 like
  • 3 in conversation