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 (August 2010, week 1)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Fri, 6 Aug 2010 08:39:36 -0400
Reply-To:     Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
Sender:       "SAS(r) Discussion" <SAS-L@LISTSERV.UGA.EDU>
From:         Suzanne McCoy <Suzanne.McCoy@CATALINAMARKETING.COM>
Subject:      Re: PASSTHRU SQL Question
Comments: To: Dave Brewer <david.brewer@UC.EDU>
In-Reply-To:  <201008061102.o76Aktl0010178@willow.cc.uga.edu>
Content-Type: text/plain; charset="us-ascii"

http://www.sas.com/technologies/dw/entdiserver/index.html

-----Original Message----- From: Dave Brewer [mailto:david.brewer@UC.EDU] Sent: Friday, August 06, 2010 7:03 AM To: SAS-L@LISTSERV.UGA.EDU; Suzanne McCoy Subject: Re: PASSTHRU SQL Question

Suzanne,

What is DI Studio?

Dave

On Thu, 5 Aug 2010 10:59:50 -0400, Suzanne McCoy <suzanne.mccoy@CATALINAMARKETING.COM> wrote:

>If you did this in DI Studio it would probably code a data set with >update, insert and modify logic instead of a proc append. It pretty much >does this as the default for slowly changing dimensions but it can be >applied any time as long as you can use or build a unique key for record >identification. > >I personally tend to do multiple steps just so I can see exactly what is >happening. I'd bust the data into staging tables like keep_no_changes, >insert_because_new, terminate_old_insert_new by using merge logic with in= >operators to compare the new data to the existing data by relational keys.


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