An Introduction: Level 1 of the Stairway to Row-Level Security

  • Comments posted to this topic are about the item An Introduction: Level 1 of the Stairway to Row-Level Security

  • Nice simple easy to follow article, thank you Steve. Just one observation; where is the link to your sample code?

    ...

  • From Article:
    These are the 3 rows with SalesPersonID = 1. The second result set shows 2 rows, each of these with SalesPersonID = 2. This second query was executed as sjones.

    From the data, it seems that the 3 rows is where SalesPersonID = 2 and the 2 rows where SalesPersonID = 1. Or am I missing something obvious here?

  • Fat Uncle Dan - Thursday, December 28, 2017 9:47 AM

    From Article:
    These are the 3 rows with SalesPersonID = 1. The second result set shows 2 rows, each of these with SalesPersonID = 2. This second query was executed as sjones.

    From the data, it seems that the 3 rows is where SalesPersonID = 2 and the 2 rows where SalesPersonID = 1. Or am I missing something obvious here?

    I noticed the same thing.  I don't think you are missing anything, just a typo.

  • We have one application with a poorly performing security implementation.  Does anybody have any guidance on the performance impact of RLS on a query?  Is it easy to avoid or mitigate performance issues?  

    RandyHelpdesk: Perhaps Im not the only one that does not know what you are doing. 😉

  • cstater - Thursday, December 28, 2017 9:51 AM

    Fat Uncle Dan - Thursday, December 28, 2017 9:47 AM

    From Article:
    These are the 3 rows with SalesPersonID = 1. The second result set shows 2 rows, each of these with SalesPersonID = 2. This second query was executed as sjones.

    From the data, it seems that the 3 rows is where SalesPersonID = 2 and the 2 rows where SalesPersonID = 1. Or am I missing something obvious here?

    I noticed the same thing.  I don't think you are missing anything, just a typo.

    typo. Corrected.

  • rstone - Thursday, December 28, 2017 10:36 AM

    We have one application with a poorly performing security implementation.  Does anybody have any guidance on the performance impact of RLS on a query?  Is it easy to avoid or mitigate performance issues?  

    This is a function, really a CROSS APPLY type function added to your queries. If there are indexes, I wouldn't expect there to be much impact from normal query performance. However, YMMV. I'd certainly like to see more people test this at higher scales with specific queries.

    If we can get  this site upgraded to 2017, I'd like to implement some RLS just to see.

  • Code now attached at the bottom of the article.

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply