Introduction
This SSIS Snack is a continuation of a couple previous SSIS Snacks: SSIS Snack: Configuring an SSIS 2005 Lookup Transformation for a Left Outer Join (please see the clarification SSIS Snack: SSIS 2005 Lookup Transformations 101) and SSIS Snack: Configuring a Conditional Split.
Landing Zone
When you use a Conditional Split to create an additional buffer, downstream connections must know which output you are trying to connect. In this case, I have an OLE DB Destination adapter to which I am trying to connect the Conditional Split:
Note that because I defined two new buffers in the Conditional Split – and renamed the Default Conditional Split Output to “Uchanged Rows” – I am prompted to select the output, and I select New Rows.
:{> Andy
My main complaint about conditional splits is that if I some how didn’t mention a condition (a condition that rarely happens) it fails the entire package, failing the entire job.
So I wonder.. if I added a final condition with the expression "1==1" and maybe sent those rows to a log file I could check every so often.. if that would fix the problem… something I’ll try in my spare time. Haha
I’d hate for that last condition to catch EVERYTHING.