Ravindra BagaleCourses & study guides मराठी Track your progress

26. Row-Level Security (RLS)

The Pune manager should see only Pune data, the Nashik manager only Nashik – and the report is the same. That is Row-Level Security. In this module we look at static and dynamic RLS, testing and the important rules. This topic comes up a lot in interviews.

What you will learn in this module

  • What RLS is and why it is needed
  • Creating static roles
  • Dynamic RLS with USERPRINCIPALNAME and a security table
  • Testing roles in Desktop and assigning members in the Service

Live story: Shraddha must see only Nashik

Suppose the same report goes to six city managers. Shraddha (Nashik) must see only Nashik. Ravindra (Pune) only Pune. Rani, the state head, sees all. Six copies of the report would be a maintenance nightmare. This chapter builds row-level security once, tests it with View as, and assigns it in the Service.

All numbers in this story are fictional practice data.

Concepts in this chapter

  1. 26.1What is RLS?
  2. 26.2Static RLS
  3. 26.3Dynamic RLS With USERPRINCIPALNAME
  4. 26.4Testing RLS
  5. 26.5Important Rules
  6. 26.6Object-Level Security

Review and practice

  1. ★Practice and Answer Key: Dynamic RLS

The chapter recap is at the end of the last concept page.

Ravi Sir's Cards: 9 revision, interview and comparison cards for this chapter · मराठी cards