December 10, 2018 by Kenneth Fisher
We’ve been doing a lot of upgrading recently and at one point had to move an instance from one 2016 server to another. In the process, we found out (the hard way) that it’s not that easy to move SSISDB (the SSIS Catalog that may or may not be named SSISDB). I mean it’s not hard, but it’s definitely not a basic backup/restore. The full BOL instructions on how to do this are here. That said, here are the elements that are involved.
- The database Master Key (yes encryption is involved)
- The password used to create the catalog
- The database/catalog itself (duh)
- The server principal ##MS_SSISServerCleanupJobLogin##
- The stored procedure sp_ssis_startup in the master database
- The SQL Agent job SSIS Server Maintenance Job
Now, to be fair a lot of this doesn’t have to be backed up/scripted out ahead of time. In my personal opinion the easiest way to do this is:
- Create an SSIS catalog on the new server.
- Restore the SSIS catalog database from the old server over the newly created catalog.
- Restore the master key either with the backup of the master key or the original password use to create the catalog on the old server.