T.R | Title | User | Personal Name | Date | Lines |
---|
284.1 | Both Work | BROKE::BOOTH | What am I?...An Oracle? | Wed Jan 04 1989 22:02 | 6 |
| SAS can interface to both Oracle and Rdb. However, when I last checked
(about a year ago), the Rdb interface was available directly from
SAS, and the Oracle interface had to be purchased from a third party.
I'm not sure if that is still the case.
---- Michael Booth
|
284.2 | How it used to work? | SNOC01::ANDERSONK | My DEBIT/CREDIT performance is lousy | Wed Jan 04 1989 23:48 | 26 |
| My knowledge is at least 12 months old, BUT check how the interface
works (both for Rdb and for ORACLE). It used to be that the Rdb
interface really was a DTR interface written in PL/1 which used
DTR$GET_PORT (right name?) to get a record at a time through a DTR
port into a SAS temp file. This is using the supplied example code
that comes from SAS.
So, program calls DTR to get a record, which layers on Rdb, and
then writes the record into a disk file. When that is all complete,
then SAS will read the disk file.... Common problem was very bad
performance, esp when programmers didnt use RSE on DTR DOMAIN but
rather put its equivalent into SAS : effect is that a sequential
read is done of all records in database relation(s) and then SAS
reads its disk file to reduce the dataset.
Another problem was that the DTR port is always called the same
name (SAS_PORT?) and so you couldnt do more than one DTR lookup
through a CDD node at a time. If you had PL/I you could modify the
example program to get around that problem.
I hope by now SAS has a much better DSRI interface! The trick is
to have SAS get data directly from the database rather than via
the intermediate disk files.
I wouldnt be surprised if the ORACLE interface is much like the
old DTR interface.
|
284.3 | call the source too | BANZAI::CAMERON | | Thu Jan 05 1989 15:51 | 18 |
| 1) Call SAS (919) 467-8000.
SAS Institute Inc.
Box 8000
SAS Circle
Cary, NC 27511-8000
They will let you know what they offer. Ask them to comment on .-1.
2) If SAS does not have a clean interface or if you want to look at a
2nd method, then try Software Interfaces RSTAT product. It is a link
between Rdb/VMS and SAS. I have not seen the product but I have talked
to the developers and read the documentation.
Software Interfaces Inc
13831 Northwest Freeeway
Suite 355
Houston, Texas 77040
(713) 460-0707
|
284.4 | And, please, post your results here | SNOC01::ANDERSONK | My DEBIT/CREDIT performance is lousy | Fri Jan 06 1989 00:38 | 1 |
|
|
284.5 | Clear the Confusion (I Hope) | BROKE::BOOTH | What am I?...An Oracle? | Wed Jan 11 1989 16:50 | 13 |
| Here's the real story.
The current version of SAS is written in PL/1. The base tape has
an Rdb access routine that works via Datatrieve. It is cumbersome
and slow. SAS is being rewritten in C. The new version will have
an Rdb interface that uses SQL. That release is expected in Q3 calendar
1989.
Meanwhile, there is a software company in Houston that can supply
a faster interface that works directly with Rdb. SAS can supply
the company name.
---- Michael Booth
|
284.6 | Prliminary documentation of 5 pages | MINDER::PICKERING | | Mon Feb 06 1989 18:02 | 9 |
| I have some preliminary documentation, dated 29 November 1988, that
describes the SAS Rdb/VMS extract procedure, called amazingly 'The
RDBEXT Procedure'.
It shows the command syntax to use. Its SQL format with an extension
for any valid VAX SQL SELECT statement for the extract.
I can send copies to interested parties as long as its not the world
and his dog.
|
284.7 | SAS Release 6 | LDP::TURKEL | Ed Turkel, Lab Info & Office Systems | Tue Feb 07 1989 18:55 | 17 |
| As stated earlier, SAS will be supporting Rdb in its C imlementation,
called SAS Release 6, currently scheduled for first revenue ship
in Fall '89. Calling it an interface is not quite accurate. What
they're doing in release 6 is a thing called 'the database engine'.
Marketing terminology aside, what this does is allow storage of
a SAS dataset directly in an SQL database. Contrast this to what's
there now, which allows data from a database to be entered (slowly)
into a SAS dataset. With the release in the Fall SAS will support
two SQL databases on VMS: Oracle and Rdb.
SAS is already talking this up to their/our customers, so feel free
to ask them for more info.
Regards,
ed
|
284.8 | update on SAS, please | AKOCOA::HAGGERTY | GIA EIS/SWS, Acton MA. | Thu Dec 13 1990 00:19 | 11 |
| Can anyone out there give me an update on SAS? Is their re-written C
version released yet? If so, has anyone used it and what was your
impression?
thanx
Kevin
|
284.9 | You've probably seen this, but... | MBALDY::LANGSTON | assimpleaspossiblebutnotsimplr | Sat Dec 15 1990 01:01 | 9 |
| ...in this week's Information Week is an advertisement on page 11. It doesn't
talk about any particular releases but says "For a SAS System executive summary,
plus details about how you can receive the SAS Syatem for a free trial, give us
a call at 919-677-8200.
SAS Institute Inc.
Software Sales Department
SAS Campus Drve
Cary, NC 27513 "
|
284.10 | SAS to RDB using Pascal and SQL Module Lang. | MSAM00::NASSER | Nasser Abdullah, SWS Malaysia | Thu Dec 20 1990 00:20 | 13 |
|
At a previous job we used SAS (pre version 6) to access RDB all of the
time. We actually wrote our own SAS to RDB interface (written in
Pascal and SQL Module language).
It was VERY easy to use, just place the SQL select statement write
in your SAS code.
If anyone would like additional information I would be happy to
accomodate thru MAIL.
-nasser-
|