THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |
in Search

Andy Leonard

Andy Leonard is an author and engineer who enjoys building and automating data integration solutions. Andy is co-host of the Data Driven podcast. Andy is no longer updating this blog. His current blog is

Speaking in Raleigh and Philadelphia This Week

Now that our 5-month old son - Riley Cooper - is on the mend, I am hitting the speaking trail again!

09 Jan 2008: I'm presenting Testing The Database to the Triangle .Net User Group (TRINUG) Wednesday evening in Research Triangle Park, NC (location details).

12 Jan 2008: I'm presenting Incremental Loads With SSIS - by far my most popular SSIS Design Pattern post - at the Philadelphia Code Camp 2008.1.

If you read this blog and are attending, please introduce yourself!

 :{> Andy

Published Sunday, January 6, 2008 6:58 PM by andyleonard

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS



Peter W. DeBetta said:

Say "hello" to Raleigh for me...

January 7, 2008 5:05 PM

andyleonard said:

Will do Peter! Keep 'em straight down south for us.

:{> Andy

January 8, 2008 7:46 AM

Kajo said:

Dear Andy,

followed your approach and it is working well.

However, on one of the SCD II pacakges, there has been a new requriement. I have to keep all columns as historical. Meaning there will not be any overwrite/updates on any of the columns.

Now, I thought, all I need to do is to remove the second OLD DB Command for updating records, and keep everything else the same.

That is:

1. OLE DB Data Source,

2. Lookup Task, set up as ignore faliure

3. Conditional Split, with only one condition: New Rows as ISNULL(primary key)

4. OLE DB Destination

Is this the best approach still?



October 1, 2008 2:15 PM

Leave a Comment


This Blog



My Latest Book:

Community Awards

Friend of Red Gate

Contact Me


Privacy Statement