Irin Later posted the following:
> Currently we have SAS 9.2 installed on my local machine and I am unable
> to access corporate DW which is located on MS SQL Server 2005.
> I am trying getting SAS 9.2 to interact with MS SQL Server 2005 through
> ODBC connection.
> SAS /ACCESS Interface to ODBC as well as SAS /ACCESS Interface to PC
> files are part of our license.
> So far my questions are the followings:
> -How can I set up SAS driver (SAS /ACCESS Interface to ODBC)?
> -Also I am not sure what the name of my SAS Serverâ€¦.Is there any SAS
> proc with which I can get this name?
> -How can I get SAS to interact with our DW through Â 'libname .. odbc?
> What kind of setting are needed?
Irin, in addition to the great advice that you already received from Dan and Roy, I would like to bring your attention to this excellent paper by fellow Westatian, Mike Rhoads:
Avoiding Common Traps When Accessing RDBMS Data
It might just help you avoid some traps up-front as you wrestle with that SQL Server database!
Irin, best of luck in all your SAS endeavors!
I hope that this suggestion proves helpful now, and in the future!
Of course, all of these opinions and insights are my own, and do not reflect those of my organization or my associates. All SAS code and/or methodologies specified in this posting are for illustrative purposes only and no warranty is stated or implied as to their accuracy or applicability. People deciding to use information in this posting do so at their own risk.
Michael A. Raithel
"The man who wrote the book on performance"
Author: Tuning SAS Applications in the MVS Environment
Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second Edition
Author: The Complete Guide to SAS Indexes
The best measure of a man's honesty isn't his income tax return.
It's the zero adjust on his bathroom scale. - Arthur C. Clarke