daniel.gaddis (4/23/2015)
>>You'll use a symmetric key to encrypt the data in the table, but remember that a symmetric key requires either a certificate or asymmetric key to protect it in the database. So, first create an asymmetric key to protect the symmetric key using the code in Listing 8.2.You are encrypting the symmetric key with an asymmetric key. I have seen other articles that encrypt the symmetric key with a certificate. Do you have any thoughts on why I should pick one over the other?
Not really. It depends a lot on your security setup in the database and server instance, but either one will be secure, as long as either you keep the secret securely or let SQL Server manage it for you.
Generally, though, you're not going to create dozens of keys and certificates, so design something that will work to protect the data from your specific threats. Keeping it simple is the best security strategy you can employ.