Home Forums SQL Server 2008 Security (SS2K8) Encryption noob with a table design general question RE: Encryption noob with a table design general question

  • February 1, 2013 at 6:53 am

    #1583432

    ahh sorry i misunderstood.

    for me, encrypted or not, it just goes to whatever normalization is proper for the data;

    Basic normalization considerations for me would be:

    data is 1:1 and rarely null, same table probably, especially if it will be typically queried witht eh main data.

    data is 1:1 with lots of nulls , a separate table for optional data

    data is 1:M, then separate table, obviously

    HOW it is stored , ie encrypted or not,isn't going to affect that decision, but i can understand how you'd think there is a logical reason to store encrypted data together.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!