Upgrading SSIS projects – part III

In the first part of the series I mentioned two methods of upgrading SSIS projects (well – packages, for now) – Application.Upgrade() and  Application.SaveAndUpdateVersionToXml(). This post is about the latter. The documentation of the method is also a bit sparse at the moment, but is self-explanatory:

Share
Continue reading »

Upgrading SSIS projects, part I

In the previous post, I wrote about migrating SSISDB database. When we migrate the database the packages still have the version of the source SSIS catalog. When you start the execution of the migrated package, you get the information like “The package was migrated from version 6 to version 8. It must be saved to retain migration changes.” This information is written to the log no matter which logging level we choose (also with None). The question is: will it blend should we upgrade the packages (or better – the projects)? And if the answer is ‘yes’ – why should we do it and what are the options? Should we

Share
Continue reading »

So, you want to migrate SSIS(DB)?

Excellent! I wanted to, and after few trials and errors I finally did! And it’s pretty easy (as with all things you know when you learn it). For a start I will warn you a bit – SSISDB isn’t the database you just backup on one server and restore on another. There are some more steps to do. The same procedure will work for migrations from version 2012 to 2017 or 2016 to 2017, I didn’t check (yet) 2014 to 2017. I also tested the migration of 2012 to 2016 version but had some problems with this when it came to upgrading database part. Will investigate it later (probably some

Share
Continue reading »