Home Forums SQL Server 2017 SQL Server 2017 - Administration Always on and SSISDB RE: Always on and SSISDB

  • March 5, 2018 at 10:22 am

    #1981984

    Perry Whittle - Wednesday, February 28, 2018 4:25 AM

    RTaylor2208 - Monday, February 19, 2018 8:53 AM

    Turns out using the backup and restore method worked adding the database on the secondary using this method,  it would be good though if someone could confirm this is the best way to do this though.

    https://blogs.msdn.microsoft.com/mattm/2012/03/23/ssis-catalog-backup-and-restore/

    you need to create a credential for the ssidb master key so that it may be read and decrypted on fail over

    This is somewhat similar to SSRS so that when two nodes share a single database they can still function over a NLB.

    My question though:  Are there any special considerations with regards to the IS Catalog?  The database issue is pretty straightforward but it isn't clear to me whether or not I have to deploy projects and packages to both servers or whether a deployment to a single server will be enough.

     I haven't read anything about this yet but this seemed like a good place to bring up a spontaneous question about it.... 🙂