June 6, 2014 at 11:41 am
Hello,
I am about to embark on a massive migration from SQL 2005 - 2008 R2. We have 200+ SSIS packages that were deployed as a file system on the 2005 box. I read a few blogs that mentioned upgrading the packages to 2008. Now, I realize when you open a SSIS package developed in 2005, VS upgrades it to 2008 automatically. I assume I do not have to manually open 200+ packages 🙂
With that being said I am not really sure how to move forward with this. We have a lot on config files and I do not have much experience with them, as the companies that I worked for in the past have had a handful of SSIS packages (not 200+).
Any help would be appreciated,
SQLTougherGuy
The are no problems, only solutions. --John Lennon
June 6, 2014 at 12:11 pm
SQLTougherGuy (6/6/2014)
Hello,I am about to embark on a massive migration from SQL 2005 - 2008 R2. We have 200+ SSIS packages that were deployed as a file system on the 2005 box. I read a few blogs that mentioned upgrading the packages to 2008. Now, I realize when you open a SSIS package developed in 2005, VS upgrades it to 2008 automatically. I assume I do not have to manually open 200+ packages 🙂
With that being said I am not really sure how to move forward with this. We have a lot on config files and I do not have much experience with them, as the companies that I worked for in the past have had a handful of SSIS packages (not 200+).
Any help would be appreciated,
SQLTougherGuy
Unfortunately, by experience, you are probably looking at 50 a week, 4 weeks of work, and no real short cuts.
The "upgrade" is only a version attribute increment, would try to bypass this step unless other things have changed.
😎
June 6, 2014 at 12:46 pm
Thanks for your reply. Are you saying that I have to manually upgrade each individual package? open them in VS?
Sorry, just found the answer... SSIS Package Upgrade Wizard
The are no problems, only solutions. --John Lennon
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply