eheh, who's first who's last to post! 😉

So, for the SSIS community here, should we say to everyone to use the conditionnal split for a CASE Statement?? Is it the best way?

SELECT CASE with conditionnal split:

Can you be more precise on how to to SELECT CASE with conditionnal split (+derived columsn for each output +union all)?

Sincerly, I think is is a little bit too much component for a soo little requirement. Correct me if i am wrong : If i have 10 case statement (for one input columns), I will have 10 "derived columns" re-united again in an Union all?

What if i have 3 sources columns being "select cased" + 1 lookup?

SELECT CASE using Lookup transfo and some reference table

About the lookup table, it is a good idea. If the clients are ok with creating some "reference table". However, if the customer requirement change slightly in time, the lookup table wont be able to adapt to this :

case when MyInput="1" then ...

when MyInput="2" and MyInput02="ok" then...

when MyInput="2" and MyInput02="hm" then...

when MyInput="2" and MyInput02="no" then...

when myInput="3" then ....

.....

Sorry to be so picky (?) but I really want to create some "best practice" for my student.

In good old SQL, it would fit in ONE little script. In SSIS, it is a complex ETL...daah

Anyway, to get to the bottom of this, I was firstly wondering if I was missing something to achieve a case statement in SSIS. For the moment, the "Script Transformation" is the cleanest and flexible way to do it.

.Net it will be!

Thanks folks!

P.S. Does Microsoft is planning to add some usefull and day-to-day used components like this one in future release of SSIS?