|
|
|
SSC Rookie
      
Group: General Forum Members
Last Login: Friday, April 05, 2013 9:32 AM
Points: 42,
Visits: 170
|
|
Or this obvious bug should be fixed!
|
|
|
|
|
Right there with Babe
      
Group: General Forum Members
Last Login: Monday, June 17, 2013 12:40 PM
Points: 748,
Visits: 905
|
|
Thank you for the article, it was interesting.
If I might add a couple of things, TDE is only available on enterprise (or developer) feature. Also, you mentioned "no peeking" at the HR password. by encasing your scripts in a GUI you shield the password from other eyes. Of course, people would have to trust you to not make your GUI log the password somewhere, but that at least removes the temptation to "peek".
--- Timothy A Wiseman SQL Blog: http://timothyawiseman.wordpress.com/
|
|
|
|
|
Valued Member
      
Group: General Forum Members
Last Login: Saturday, June 15, 2013 12:17 PM
Points: 52,
Visits: 215
|
|
Thanks for a great article. I tried it out and it works OK.
Now I was just wondering about backups. We use a third party tool for backups which does its own encryption while taking the backup (AES128). How do you think using TDE will affect restores of databases backed up using this tool?
|
|
|
|
|
SSCertifiable
       
Group: General Forum Members
Last Login: Today @ 3:36 AM
Points: 5,242,
Visits: 11,263
|
|
good article but unfortunately it makes the same mistake regarding master keys that others make.
To restore a TDE protected database to another server you do not need to backup and restore the database master key held in the master database. if a database master key doesn't already exist on the target server create one before restoring the certificate backup from the source server, but it is in no way tied to the certificate or the restore.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs"
|
|
|
|
|
Forum Newbie
      
Group: General Forum Members
Last Login: Friday, August 17, 2012 2:52 AM
Points: 1,
Visits: 17
|
|
Many thanks for this article and scripts - would like to add this though, make sure you have no long running transactions on your database that you want to encrypt before encrypting. DBCC OPENTRAN; on the relevant database will let you know the longest one. Didn't find this out until we run it on our Production database after tests etc - 18 hours later and no movement - once i killed off that transaction that had be open (for days!) completed in 30 mins.
|
|
|
|