March 22, 2017 at 8:46 am
On old server
USE SSISDB
BACKUP MASTER KEY TO FILE = D:\Keys\SSISDB_Key'
ENCRYPTION BY PASSWORD = 'mypwd'
In the new server I created the SSISDB catalog and restored the SSISDB and then restored the master key as follows
USE SSISDB
RESTORE MASTER KEY FROM FILE = 'E:\MasterKeyBackup\SSISDB_Key'
DECRYPTION BY PASSWORD = 'mypwd'
ENCRYPTION BY PASSWORD = 'mynewpwd'
FORCE
I go the following message.
The old and new master keys are identical. No data re-encryption is required.
March 23, 2017 at 6:58 am
what is your question
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
March 23, 2017 at 8:45 am
If your packages won't work, compare the IS_TRUSTWORTHY setting for the original DB and the restored DB.
This setting is off by default on the restored DB.
Not much on this on the net even on MS websites.
RUN..
USE master
GO
ALTER DATABASE SSISDB SET TRUSTWORTHY ON
This will do the trick if that is the issue.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply