March 15, 2012 at 10:51 pm
Hi Team,
We need to encrypt sensitive data after database has been restore....we already implement sql server inbuilt encryption function to encrypt data...but when restore happens we lost encryption or we need to re-build master key, certificate and encrypt data....etc...
so, when restore happens which is the best solution to encrypt data (either we create SP to encrypt data / used in-build sql encryption function )?
🙂 🙂 🙂
Amey ghag
<a href='http://' class='authorlink' target='_blank'></a>
March 16, 2012 at 1:15 pm
I'm not following here. You shouldn't never lose the database master key. You should be protecting it in accordance with the guidance in Books Online (BACKUP MASTER KEY). In this case both the file and the password used would need to be protected.
You also shouldn't need to regenerate the database master key. If you're doing a restore to a new server, you simply need to associate the database master key with the service master key. You can do this with the ALTER MASTER KEY command, but you will need to know the password that was used to generate the database master key. Therefore, you need to store that password somewhere safe.
If all the subsequent keys chain from the database master key, once you get the database master key connected with the SQL Server such that SQL Server can open it automatically, you should be set again.
K. Brian Kelley
@kbriankelley
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply