Andy Leonard

Andy Leonard is CSO of Linchpin People and SQLPeople, an SSIS Trainer, Consultant, and developer; SQL Server database and data warehouse developer, community mentor, engineer, and farmer. He is a co-author of SQL Server 2012 Integration Services Design Patterns. His background includes web application architecture and development, VB, and ASP. Andy loves the SQL Server Community!

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).

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

:{> Andy

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

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? Thanks, Kajo October 1, 2008 2:15 PM