Question

I read this on msdn:

Views let different users to see data in different ways, even when they are using the same
data at the same time. This is especially useful when users who have many different interests and skill levels share the same database.

For example, a view can be created that retrieves only the data for the customers with whom an account manager deals. The view can determine which data to retrieve based on the login ID of the account manager who uses the view.

My question:

For the above example , i would have to have a column named Userid/LoginId on my table on which the view is created so that i can apply a check option in the view for this column. and then if a user with a name not in that column tries to enter data , then he/she is blocked.

Answer 1

Yes, you are right. You should

• add a column with the user’s login or database user name (say you call it username),
• each row should have username populated with the login or database name of the person who is allowed to see that row
• you can then build a view where you use the builtin functions SUSER_SNAME() (for logins) or USER_NAME (for database names) in your WHERE clause to filter only the rows the user is allowed to see

See Granting Row-Level Permissions in SQL Server (ADO.NET).