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 problem I want to solve is automation of the SSIS project upgrade. Previously I wrote about the options to use Application.Upgrade() or Application.SaveAndUpdateVersionToXml() methods. This post is about the first of those options.

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.”

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.