Hello Ann,

>> ...but why should good encryption be very expensive?

> Because the database has to encrypt and decrypt each piece of data
> as it goes in and out of the database. That's an absolutely
> critical path and very heavily travelled. We've talked about page
> level encryption - cheaper because it's done only when a page is
> read or written. That doesn't help in this case.

Do you mean en/decrypting the page as a whole when it is written or
read? As far as I can read back the thread (which is not very far
at this moment) the person you responded to (IB/FB List == Marcus?)
wrote:

>> Are a good feature have record encryption based on user or roles

...which I interpreted as "encryption of records based upon the user
that should have access to those records", i.e. using different
ecncryption keys for different users. I must admit however that I also
interpreted "record encryption" as "field encryption" or rather "field
data encryption". Which is not too expensive on the client side.

It started to dawn on me that we were probably talking about two
different things when you asked the other guy if he'd ever thought
about client side encryption... ;-)


Greetings,
Paul Vinkenoog