Updating ssis packages

Even though the package will have been updated prior to re-deploy to handle the new metadata, I still have to go onto each system and update the package AGAIN before it will recognize the new metadata. In BIDS 2008, a refresh of metadata on one system would persist to any system it was deployed to.Now, if I change the connection manager prior to deploying it, I have to go back and re-do the metadata refresh before I can send it up.I have existing packages that hit objects on these systems.Every time I have to make a change that affects metadata, it's not enough that I update the objects on the target system, then update the SSIS package that points to the system, and then re-deploy the package on the system.

The first conversion is more of a Visual Studio upgrade and the second specific to SSIS.Many of you may now or in the future have the need to upgrade your SSIS packages to the new SQL Server 2012 SSIS.Luckily, upgrading from SSIS 2005 or 2008 isn’t nearly as painful as you may have experienced upgrading old DTS (SQL Server 2000) packages.If you’re considering the upgrade to 2012 here are some of the new features you have to look forward to: There is far more than I could list here but you can do a search for “What’s new in SSIS 2012” just as easily as I can .The upgrade process from 2005 or 2008 to SSIS 2012 is actually very straight forward.

Leave a Reply