Re: Encrypting Data in SQL 2000
- From: "Arnie Rowland" <arnie@xxxxxxxx>
- Date: Thu, 13 Jul 2006 12:43:44 -0700
Very limited.
If using a .NET applicaiton, there is a rich encryption library that could
be used at the application level to encrypt data before it is stored in the
server, and decrypt it after if is retreived.
And there are several third party 'Add-ins' to allow encryption via extended
procedures.
A very crude 'hiding (and generally ineffective) scheme would be to use one
of the checksum() functions and do a one-way process. You couldn't 'decrypt'
it but you could use a comparison to verify if an input value matches.
As far as I know, the application level method is the only way to keep a
determined DBA (or Admin) from being able to access the encrypted data AND
the means to decrypt it. (But then, the question is "Is that a wise
decision?, Are you feeling lucky? Go ahead, make my ..."
--
Arnie Rowland*
"To be successful, your heart must accompany your knowledge."
"Steven" <Lazans@xxxxxxxxx> wrote in message
news:eDdtTMrpGHA.4812@xxxxxxxxxxxxxxxxxxxxxxx
What is the recommended way to store data in SQL Server 2000 encrypted so
not even DBA can see the values? I know SQL 2005 has encryption at the
row level, but what are my options in SQL 2000?
Thank you,
Steve
.
- Follow-Ups:
- Re: Encrypting Data in SQL 2000
- From: Steven
- Re: Encrypting Data in SQL 2000
- References:
- Encrypting Data in SQL 2000
- From: Steven
- Encrypting Data in SQL 2000
- Prev by Date: Encrypting Data in SQL 2000
- Next by Date: Re: Truncate permission?
- Previous by thread: Encrypting Data in SQL 2000
- Next by thread: Re: Encrypting Data in SQL 2000
- Index(es):
Relevant Pages
|
