[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sas-l
Subject:    Re: EG4.1 - Using non-SAS data nodes
From:       Sigurd Hermansen <HERMANS1 () WESTAT ! COM>
Date:       2006-11-30 23:41:45
[Download RAW message or body]

Tree Frog:
Welcome to the world of SAS/Access engines ....

Better to avoid turning MS SQL Server tables into SAS datasets.... A SAS
libname connection string for the OLEDB engine, or a CONNECT TO string
for 'pass-thru' queries, makes SQL Server tables serve the same function
as SAS datasets. In fact, with a libname connection string, tables to
which you have access rights appear in the Explorer window, and you can
view metadata or view the table itself.

As I recall, EG gives you the same access to a 'data node'. With full
access to the SQL Server table, you don't have any reason that I can see
to turn the data node into a SAS dataset. Simply use it as such for what
you would ordinarily do with a SAS dataset!
Sig

-----Original Message-----
From: owner-sas-l@listserv.uga.edu [mailto:owner-sas-l@listserv.uga.edu]
On Behalf Of Tree Frog
Sent: Monday, November 27, 2006 9:52 PM
To: sas-l@uga.edu
Subject: EG4.1 - Using non-SAS data nodes


Hi all

I'm accustomed to working directly with code and to using SAS data sets.
I've recently started using EG4.1, and I'm happy that I can bring in
table from a SQL Server database using the OLEDB option in the Open
menu.  However, how can I now interrogate that data node using SAS code?

I notice that when I run any menu function on the data, EG generates
code that first creates a temporary SAS dataset and then performs the
operation on that dataset.

How can I, writing code (i.e. not relying on pointing and clicking in
EG), perform the step that turns the data node into a SAS dataset?

Many thanks - I realise this is probably a dumb question & I'm missing
something obvious...

TF

[prev in list] [next in list] [prev in thread] [next in thread]