• dnonyane (11/28/2014)


    now as long as the users don't know these stuff they won't be able to interpret it.

    Security by obscurity does not work.

    What exactly do you mean by 'adding encryption keys to the column'? Because the way SQL encryption works is that you open the key, use the encryption function then insert/update the encrypted value. Anyone with rights on the key/certificate can open it and decrypt the data, that includes all sysadmins and db_owners. Encryption is not a property of the table or column

    You shouldn't be relying on 'the user doesn't know this stuff'. Encryption should protect data even from someone who knows exactly how the encryption hierarchy in SQL works, knows all the functions and is familiar with the database schema,

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass