How to handle added input data colums without having to maintain multiple versions of SSIS packages?

Posted by GLFelger on Stack Overflow See other posts from Stack Overflow or by GLFelger
Published on 2010-04-02T14:51:52Z Indexed on 2010/04/02 14:53 UTC
Read the original article Hit count: 161

Filed under:
|
|

I’m writing to solicit ideas for a solution to an upcoming problem.

The product that provides data to our ETL process currently has multiple versions. Our clients are all using some version of the product, but not all use the same version and they will not all be upgraded at the same time.

As new versions of the product are rolled out, the most common change is to add new data columns. Columns being dropped or renamed may happen occasionally, but our main focus right now is how to handle new columns being added.

The problem that we want to address is how to handle the data for clients who use an older version of the product. If we don’t account for the new columns in our SSIS packages, then the data in those columns for clients using an older product version will not be processed.

What we want to avoid is having to maintain a separate version of the SSIS packages for each version of the product. Has anyone successfully implemented a solution for this situation?

© Stack Overflow or respective owner

Related posts about ssis

Related posts about versions