Learn about how to implement row-level security in the database tier of your application. Learn the limitations and how it integrates with other features.
- [Narrator] The first part of integrating row-level…security in your application is really straight forward.…You just have to design it into the database.…You do have to figure out a way to make sure SQL server's…getting the proper session context from your application…and that can be a little bit tricky…just because SQL server needs to know the user or the thing,…whether it's an application or a username,…that it's filtering on, or even a session ID,…so that it can do the filtering.…So you just need to figure out your function,…what you want to filter on,…and then how you filter, or block even.…
So this is going to let you control access to the rows…in your database tables based on the characteristics…of the user who's executing the query,…so you can have this be group membership, execution context,…you can even filter by application like I mentioned,…so maybe users could have full access…to the data through your application,…but if they are connecting through Excel or something else…you eliminate the rows that you can see.…
- Designing row-level security
- Using views to implement row-level security in SQL Server pre-2016
- Data encryption
- Configuring Always Encrypted
- Dynamic data masking