LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (March 2008, week 5)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Mon, 31 Mar 2008 12:41:25 -0400
Reply-To:     Michael Raithel <michaelraithel@WESTAT.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Michael Raithel <michaelraithel@WESTAT.COM>
Subject:      Re: SAS/Oracle Processing Question
In-Reply-To:  <200803282134.m2SIcj1N026483@malibu.cc.uga.edu>
Content-Type: text/plain; charset="us-ascii"

Dear SAS-L-ers,

Richard Wright posted, in part, the following helpful information:

<<Richard's entire original posting can be found beneath the Sig line>>

> 1. A couple of months ago, I read a white paper on the SAS > website that they were starting offload some of the > processing onto the server. I don't have it handy, but you > might see if you can find it. > Richard, yea; that was a very interesting white paper, indeed! There was a paper on in-database processing presented at SAS Global Forum 2008:

SAS(r) In-Database: Deeper Integration between the SAS System and Database Management Systems, by David Shamlin: http://www2.sas.com/proceedings/forum2008/315-2008.pdf

...and a second paper by the Teradata folks:

Driving Competitive Advantage with In-Database Analytics, by Mike Rote http://www2.sas.com/proceedings/forum2008/062-2008.pdf

Perhaps this will eliminate the need for you to dig for that paper reference that wasn't on the tip of your brain when you posted!

Richard, best of luck in all of 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" E-mail: MichaelRaithel@westat.com

Author: Tuning SAS Applications in the MVS Environment

Author: Tuning SAS Applications in the OS/390 and z/OS Environments, Second Edition http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=58172

Author: The Complete Guide to SAS Indexes http://www.sas.com/apps/pubscat/bookdetails.jsp?catid=1&pc=60409

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ As long as you derive inner help and comfort from anything, keep it. - Mahatma Gandhi +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

<<Richard's entire original posting>>

> Couple of quick ideas: > > 1. A couple of months ago, I read a white paper on the SAS > website that they were starting offload some of the > processing onto the server. I don't have it handy, but you > might see if you can find it. > > 2. There was a presentation at our SCSUG last fall about > replacing SQL queries with hash tables - "How Do I Love Hash > Tables? Let Me Count The Ways!" Judy Loren > > 3. Could you break up you query a little bit: > > create table local.claimmerge as > select vars > from > (select DISTINCT s1.id > from local.eligibility(KEEP=id) s1, local.type1claims(KEEP=id) s2 > where s1.ID=s2.ID) a, > local.eligibility, local.type1claims > where a.id = eligibility.id and a.id = type1claims.id > order by ID; > > 4. Modify it further: > > proc sql noprint; > create table local.claimmerge as > select vars > from local.eligibility, > dw.type1claims > where (eligibility.ID=type1claims.ID) and (type1claims.date between > 1/1/2004 and 12/31/2006) > order by ID; > quit; >


Back to: Top of message | Previous page | Main SAS-L page