SSISDB packages move

  • Hi,
    Looking for an advice in SSIS migration from 2012 to new version of SQL

    packages exists in all places..SSISDB,MSDB.Filestore .
    Current system is 2012 and is migrating to 2016(some machines) and 2017.

    1)migrating packages in SSISDB--> a db restore from 2012 to 2016/2017 will do the upgrade and will make it ready for execution? or have to export each project and open in VS and upgrade and re deploy?

    2)migrating packages MSDB--> other than exporting to file system and importing to 2016/17 each package, is there any other step pr any shortcut, conidering a large number of packages exists.

    3)migrating packages in file store--> open each package in data tools(VS) then upgrade each packge, right click and migrate and redeploy? or any other way/ step to do?

    appreciate if any one can comment/advice
    thanks

  • any comments pls..

  • on VS upgrade each package and solution to latest version.
    some may not upgrade correctly which means they would not run at all on new server even if the inplace upgrade would work.

    take the opportunity to remove all usage of packages on msdb to be either filesystem or SSISDB (pros and cons in both).

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply