Timeline for Upgrading SSIS packages
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 4, 2016 at 13:58 | vote | accept | iDevlop | ||
| Sep 30, 2016 at 20:08 | history | edited | billinkc | CC BY-SA 3.0 |
ranty mcranterson
|
| Sep 30, 2016 at 18:19 | comment | added | iDevlop | You are right, and I never noticed it. The SQL Server version is 12 (2014) and the SSIS is 10 (2008). I don't know how that can happen - I never was part of the server's setup & upgrades. Thanks for pointing that, now I'll see if/how I can upgrade that SSIS. | |
| Sep 30, 2016 at 15:12 | comment | added | billinkc | The screenshot shows the Integration Services explorer is connected to a 2008 R2 instance. Soooo if they're already on 2012, did I misunderstand the root question? | |
| Sep 30, 2016 at 15:08 | comment | added | iDevlop | The packages are already on the 2012 instance, they probably survived some upgrades. They were created using Import Export wizard. No source control here, I am the only dev. I don't think I will receive a second server for testing neither. | |
| Sep 29, 2016 at 15:51 | history | answered | billinkc | CC BY-SA 3.0 |