One of the file I used to receive under a specific codepage has sudenly switched codepage. Not too bad, I tought, I just go to the configuration package and change the codepage for my flat file connection. If only it was that easy! next my column mapping in my flat file source are screewed because the codepage does not correspond to the codepage of the flat file connection. Easy to change. Not so easy to configure properly. What I am wondering is if there is a proper way to configure the codepage within the complete ssis package. I could use a variable to contain my codepage and use expressions to define the codepage of every columns. Nah! expressions does not seems to be available there. I could output every column to a config file and change it there. Nah! doesn't seem feasible either. Anybody had a similar situation and figured a proper strategy to make the ssis codepage configurable? Maybe there is something I am overlooking? I would really enjoy not having to redeploy SSISs every time the code page changes.

As far as I know, unfortunately, once you changed the code page the metadata needs to be rebuilt down the chain, therefore, you need to refresh the whole flow. Update, refresh remap, save.Arthur My Blog

You can edit the XML and find/replace all. I would caution you to save a backup copy before doing this however.

Anthony, I do not think there is a way to export the column output of a data source to the package configurations. This is partly where my issue comes from. Let me know if you know otherwhise.

I'm sorry I misunderstood the question, I didn't realize you wanted to do it Dynamically. You are correct here - you do have one other option being you could store the package on the filesystem instead of the MSDB and use a powershell script to find/replace all the instances of the code page in the XML prior to execution. It's probably about the only option though.