SQL Clone
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in

Moving SSISDB is not as easy as it sounds

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:

  1. Create an SSIS catalog on the new server.
  2. Restore the SSIS catalog database from the old server over the newly created catalog.
  3. 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.


My name is Kenneth Fisher and I am Senior DBA for a large (multi-national) insurance company. I have been working with databases for over 20 years starting with Clarion and Foxpro. I’ve been working with SQL Server for 12 years but have only really started “studying” the subject for the last 3. I don’t have any real "specialities" but I enjoy trouble shooting and teaching. Thus far I’ve earned by MCITP Database Administrator 2008, MCTS Database Administrator 2005, and MCTS Database Developer 2008. I’m currently studying for my MCITP Database Developer 2008 and should start in on the 2012 exams next year. My blog is at www.sqlstudies.com.


Leave a comment on the original post [sqlstudies.com, opens in a new window]

Loading comments...