November 17, 2015 at 7:42 am
We have an XML that gets updated every month, mostly just adding additional fields. This XML is used by hundreds of SSIS packages and every time we refresh the XML we have to remap all the existing mappings in our data flow. Is there a way to not break the columns already mapped? We are using 2008 r2 if that matters.
This seems like such a simple concept but I can't find an answer.
Thank you,
Matt
November 17, 2015 at 8:48 am
If you are not using the new elements/attributes, consider remapping the new XML into the one you want, perhaps using XSLT
Gerald Britton, Pluralsight courses
November 17, 2015 at 9:42 am
Hi Gerald,
That's a good idea, not all of the packages always use the new attributes. Is there a solution for the packages that are going to use the new additions? I'm possibly going to try and parse the dtsx package to see if its a simple solution there.
November 17, 2015 at 10:57 am
o103452 (11/17/2015)
Hi Gerald,That's a good idea, not all of the packages always use the new attributes. Is there a solution for the packages that are going to use the new additions? I'm possibly going to try and parse the dtsx package to see if its a simple solution there.
If your packages need to use the new elements/attributes, you will need to modify them regardless. OTOH, if you generate them with BIML, you can make that a less painful experience.
Gerald Britton, Pluralsight courses
November 17, 2015 at 11:11 am
I believe SSIS 2012 "Fixes" this issue with remembering the last working version of the remapping when a source or destination changes. I'll test and update back incase others are looking for the answer.
http://blogs.msdn.com/b/mattm/archive/2011/08/08/column-mapping-improvements-in-denali.aspx
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply