![]() As a result, you'll get the same error as in the previous case. It's the same problem as the previous case: we don't have the correctĬertificate. It'sĭifferent, but that's not the reason we'll fail with respect to the restore. Note the difference in the password for the database master key. MOVE 'RecoveryWithTDE_log' TO N'C:\SQLData\RecoveryWithTDE_2ndServer_log.mdf' WITH MOVE 'RecoveryWithTDE' TO N'C:\SQLData\RecoveryWithTDE_2ndServer.mdf', Since we don't have the corrected certificate, this will fail, too.įROM DISK = N'C:\SQLBackups\RecoveryWithTDE_Full.bak' Though this certificate has the same name, the restore won't work Note the difference in passwordsĮNCRYPTION BY PASSWORD = 'SecondServerPassw0rd!' Let's create the database master key and a certificate with the same name You can check the status of the encryption with the ![]() That as we look at the "gotchas" in the restore process.Įven on databases that are basically empty, it does take a few seconds toĮncrypt the database. Same password is not required, but having the same certificate is. Restore on the second server, I'm going to use a different password. This starts the encryption process on the database. Create the DEK so we can turn on encryptionĮNCRYPTION BY SERVER CERTIFICATE TDECert Back up the certificate and its private keyĮNCRYPTION BY PASSWORD = 'APrivateKeyP4ssw0rd!' ![]() Create the certificate we're going to use for TDE ENCRYPTION BY PASSWORD = 'FirstServerPassw0rd!'
0 Comments
Leave a Reply. |