Updating ssis packages 20 second sex chat
There are a few things to note that are not upgraded automatically through the native upgrade steps.
The following are not upgraded and may need extra attention: To get started open your old SSIS solution in SQL Server Data Tools (new name for BIDS), which will automatically launch a conversion wizard.
I also had all the validation turned on, but that didn't help.
So, to try it out, I dropped the whole project from the production box (we use SVN for our changes so I can get it back to that revision) and re-deployed the project all over again.
So if a configuration overrides a connection it will still have the old provider. Review the actions that will be taken by the wizard then click Finish.
A successful conversion should look similar to the below image.
At this point I'd expect that there would not be a required refresh of the metadata, as the schema of the destination table in UAT matches the one in DEV, to which the package was pointed when it was last refreshed.
Since you are using SQL 2012 you should probably be using environments (thanks @Martin Smith) I had similar issue before with my SQL Server 2012 Enterprise Edition production box.
Even though I would make sure everything was refreshed under SSIS packages before I deployed to the production box, when it executed on the production box it would just not work, saying object doesn't exists.
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.