• david_h_edmonds - Tuesday, February 20, 2018 9:57 AM

    Hi, I have come up with a different solution, not quite as sustainable with high data voulmes but as the volume will be relatively low for this process, I have the data source as an SQL statement and used case whens so that the fields exist when the data is imported into the data flow.
    What are the pitfalls of this?

    Cheers

    Dave

    This is a decent solution ... there are no particular pitfalls.
    I would, however, suggest that you consider creating 'DerivedStatus' as a permanent physical mapping table and using that in your query, rather than CASE.
    If you decide that you really want to code all of this in SSIS instead, it would be simple enough to write a few lines of code in a Script Component to implement the logic for you. Much easier to read and understand (IMO) than a derived column containing multiple nested (condition?True:False) expressions.

    If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.