SQL server Column level security

Priyanka Kshatriya 21 Reputation points

I want to implement column level security to tables in SQL server 2008 and 2014 .What are the best options for this kind of scenario .

SQL Server
SQL Server
A family of Microsoft relational database management and analysis systems for e-commerce, line-of-business, and data warehousing solutions.
9,750 questions
0 comments No comments
{count} votes

Accepted answer
  1. Sean Gallardy - MSFT 1,876 Reputation points Microsoft Employee

    Column level security is a broad statement, but it's generally meant how do I allow or not allow users to query or view that data. It could also mean how do I protect that data, such as encrypting it or masking it.

    For allowing or not allowing, those are permissions. SQL Server have a host of permissions which can be given to user made roles so that it's easily reusable, you'll want to start here for those. These work even from 2008, though 2008 is out of support so I would not use that version, 2014 is out of mainstream support and wouldn't do any new work on that version either.

    Protecting a column via encrypting it you have column level encryption and Always Encrypted. Column level encryption is available in all versions, Always Encrypted will require 2016+.

    Data masking can be done via dynamic data masking and is available in 2016+.

    So basically, for 2008->2014 you have permissions and column level encryption available to you.

    1 person found this answer helpful.
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Cris Zhan-MSFT 6,566 Reputation points


    For the instances of SQL Server 2008 to 2014, please consider column level permissions and Column Level Encryption.
    Or create the view that only queries specific columns.

    0 comments No comments