The reason I don't say to backup and restore the SMK, as the other answer shows, is that it affects all of the databases on the instance whereas just fixing the broken one won't cause any other issues on any current databases. Then it will add the encryption through the SMK back to the DMK so that automatic key decryption will work. ![]() At this point the SMS site backup should start, refer to the smsbkup.log file (located in D:Program Files (x86)Microsoft Configuration ManagerLogs) for details such as. This will drop the encryption of the DMK by the SMK, since it can't decrypt it on the new instance. Open up Administrative tools/Services and locate a service called SMSSITEBACKUP, select the service, right click and choose Start. ![]() Open master key decryption by password = 'MyPassword'Īlter master key drop encryption by service master keyĪlter master key add encryption by service master key When you restore the database to the new instance, run the following: use databasename Since you're migrating to a different instance of SQL Server you can still access the DMK through the password, however automatic key decryption will no longer work because the SMK has changed. You have a database master key (DMK), which is protected by both the service master key (SMK) and a password. ![]() I need to migrate this database to another instance of SQL, but after I migrate the database, I cannot decrypt the information.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |