Solved

Can't see tables in the SAS library even though the ODBC connection is successfully assigned

Posted on 2009-03-31
5
2,251 Views
Last Modified: 2013-11-16
I have successfully assigned a SAS ODBC connection which points to a SQL server 2005 database and it connects successfully.

However I can't see the tables in my libref library. Does anyone know why this is? Is it an issue with SQL Server 2005 database permissions?

I can bring the SQL Server tables into SAS and use them only if I know the table name.
LIBNAME SQLDB ODBC
PROMPT = "UID = NAME; PWD = NAME; DSN = NAME; SERVER = IPADDRESS; DATABASE = DBNAME; ";

Open in new window

0
Comment
Question by:geoffcoles
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
5 Comments
 
LVL 4

Expert Comment

by:wigmeister
ID: 24049517
Have you looked at the table schemas?

Maybe this doc will help.  It appears you have your connection set up without any issue.  The schema should allow you to see a list of tables in the database.  You can either use the SAS Query Window or SQL Passthrough, depending on what platform you are running SAS on.  Look at pages 11-13 for an explanation.  Hope this helps.

support.sas.com/techsup/technote/ts765.pdf
0
 

Accepted Solution

by:
geoffcoles earned 0 total points
ID: 24076510
In the end we got it working. It involved checking our permissions on the Sql server database and also modifying the connection string to the following format so that it would work with windows authentication to sql server:

LIBNAME SQLDB ODBC
NOPROMPT= "DSN=mydsnname;" SCHEMA=myschemaname;

0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A Stored Procedure in Microsoft SQL Server is a powerful feature that it can be used to execute the Data Manipulation Language (DML) or Data Definition Language (DDL). Depending on business requirements, a single Stored Procedure can return differe…
Recently I was talking with Tim Sharp, one of my colleagues from our Technical Account Manager team about MongoDB’s scalability. While doing some quick training with some of the Percona team, Tim brought something to my attention...
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
This is a high-level webinar that covers the history of enterprise open source database use. It addresses both the advantages companies see in using open source database technologies, as well as the fears and reservations they might have. In this…

622 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question