August 14, 2008 at 6:12 am
Hi,
I want to encrypt and decryp the data as my database size is of
> more then 90 gb and every week 4.5 million records gets inserted and same no of records gets updated.
> we do archive the data......
> .........i want suggestion from u guys as u are having experince
> in such senarios plz let me no how shud i go for it... i want
> only 5 columns of each table shud get encrypt and decrypted ....
> ....i no abut 2005 asyymetric but in that len of the column are
> getting increased i dnt want to increase the size and there might
> be a perofrmance issue while inserting the data as i hav not tried yet....
> ...... and 1 more thing do i hav to make changes in all the procs and fuc
> plz give me some suggestion or provide me a proc so that it can
> automatically get encrypts while selecting and gets decrypt while
> inserting and updating records ...... some of the users have only
> select permission ...
August 14, 2008 at 9:08 am
This is not a question that can easily be answered on the forums. But in general:
- You are most likely going to have to increase size. That's probably not avoidable.
- If any of the columns to be encrypted are used in WHERE clauses now, yes, you will have a performance hit. Pretty much unavoidable. For instance, if you were keying on account number but account number needs to be encrypted, you can't do this now without a table scan.
- Yes, you'll have to alter your stored procs and everything else that accesses data. Encryption is easy to build in at the start, but hard to retrofit.
Are you trying to encrypt the data while it is "at rest," or do you need to keep it encrypted while the SQL Server is on-line? If it's the first case, SQL Server 2008's Transparent Data Encryption (TDE) is an option, as is the use of Encrypting File System (EFS) at the OS level for all versions.
K. Brian Kelley
@kbriankelley
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply