Proprietary data in SQL2005
- From: "cpnet" <cpnet@xxxxxxxxxxxxxxx>
- Date: Wed, 15 Nov 2006 13:50:37 -0500
I'm trying to understand what I can do to protect proprietary data in SQL
2005. I have an application that currently uses Paradox and I plan to move
it to SQL 2005. Most users will start off with SQL 2005 Express, but will
eventually move to a 'full' version of SQL Server. Paradox allows me to
encrypt whole tables. I know it's not very good security because someone
can still do memory dumps etc. but in combination with licensing agreements
it's probably sufficient in my case to protect proprietary data stored in
the database. Can I achieve something similar in SQL 2005?
I see that I can encrypt data in specific columns, but I'm guessing that
those columns can't be indexed? (Or if they were indexed, it would have to
be the encrypted values rather than the original unencrypted values that
would actually be indexed thus making the indexing less useful)? It doesn't
seem like there's any way to encrypt a whole table?
In some of the stuff I've read, I get the sense that if I create a named
instance of a new SQL Server (Standard or Express), I can set up my instance
to only use SQL Authentication. Then I can prevent the Computer Admin of
the machine where SQL Server is installed from using his/her Windows
Authentication to access the database or named instance of the server. The
only way to configure the server or it's databases would be to know the SA
password and use SQL Authentication to log into the SQL server instance. Is
this correct? And, what does this gain me? How hard would it be to take
the database from my named instance and move it to a different SQL Server
Instance and then gain access to it?
.
- Follow-Ups:
- RE: Proprietary data in SQL2005
- From: Charles Wang[MSFT]
- RE: Proprietary data in SQL2005
- From: Charles Wang[MSFT]
- RE: Proprietary data in SQL2005
- Prev by Date: sql server proxy acct
- Next by Date: OK - I'm stupid....How do you create a user?
- Previous by thread: sql server proxy acct
- Next by thread: RE: Proprietary data in SQL2005
- Index(es):
Relevant Pages
|