Re: Views

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Toby Herring (therring*_at_*teletrack.com)
Date: 10/06/04 

Date: Wed, 6 Oct 2004 11:17:49 -0400

I think the question should be why you're encrypting data and taking the
(significant) encryption/decryption performance hit when you're providing
the decryption logic in the same database as the encrypted data? It's not
like you're really going to be protecting anything from anyone that gains
access to your database. 

-- 
Toby Herring
MCDBA, MCSD, MCP+SB
Need a Second Life? 
http://secondlife.com/ss/?u=03e0e5b303c234bf08e80ee40119a65e
"Justin Drennan" <justin@nospam.com> wrote in message 
news:-L6dnQDXBd--Zv7cRVn-rw@is.co.za...
> Hi Guys,
>
> There has been a change requested here, whereby data in our tables is 
> going
> to be encrypted. This will impact heavily, as joins as well as data 
> viewing,
> using encrypted data could be problimatic. A suggestion has been made:
>
> 1) Allow for encrypted data, and have all tables renamed ie. UserTable =
> UserTable_Encrypt
> 2) Create views, (which contain the decrypting functioanlity), name the
> views the original tanle names
>
> All existing queries will therefore run on views.
>
> Does anybody have any recomendations? or other ways to do this?
>
> What sort of impact will views have on database speed?
>
> Thanks,
> Justin
>
>

Relevant Pages