Practical encryption question with SQL 2005 back end

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Jim M

    #1

    Practical encryption question with SQL 2005 back end

    I'm porting my Access 2003 backend to SQL Server 2005 in order to
    accomodate more users with more stability. I want to encrypt the
    columns with client names, addresses and phone numbers because we are
    storing confidential info on them in other tables. Am using and MDB
    file (OBDC) rather than an Access project to avoid changing scads of
    code.

    I looked at the Microsoft Code examples about how to have SQL Server
    encrypt data. Question:
    I'm not sure how to do this practically. I have several combo boxes in
    the front end that need to be populated by the clients name which need
    to be accessed frequently. Do I decrypt it into a view that becomes
    the record source for the combo boxes? Wouldn't his expose my data if
    the Server becomes compromised? How do I do this securely, but still
    allow all users frequent access to this.

    I get how to create and encrypt a column of data, but not sure where
    the key gets stored. I assume it must go somewhere in the front end? I
    can't really allow serious performance delays. My client list has
    around 10,000 records.

    Are there any examples of making something like this work that I can
    look at? I am mostly befuddled by SQL Server 2005, but really
    appreciate its stability.

    Thanks!
    Perhaps a good reference for utilizing Access databases (not projects)
    and SQL Server 2005?

Working...