February 29, 2008 at 10:03 am
I'd like to know if anyone has any statistics for quantifying the impact that encrypting SQL Server communications with signed certificates will impose on a server.
For instance, something like "by enabling encryption all communication will be slowed by x% due to the overhead".
I don't know if this information is available or possible to get, so any help would be appreciated.
Thanks,
John
February 29, 2008 at 8:22 pm
I don't know of any stats on this, but I have always wondered why encrypt at the SQL Server? This means that the data is now unencrypted on the wire to and from the SQL Server. Why not encrypt/unencrypt in the app? Then your data is protected the whole way.
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
March 2, 2008 at 10:41 am
There are reasons to encrypt in the database, protects data in backups, loss of database, etc. However if it's a big deal, the wire should be encrypted as well. There's less concern of that with internal applications as most networks are switched, it would require a few people to trace the data on the wire, etc.
There's no way to tell what the load will be. The CPU will have to decrypt and encrypt, you have limits on some encryption with data sizes (asymmetric keys), you don't necessarily want to encrypt all data, etc. It requires some testing to determine the load for your application.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply