July 13, 2015 at 4:38 am
Comments posted to this topic are about the item Stairway to SQL Server Security Level 10: Row-Level Security
July 29, 2015 at 6:48 am
In the first Tip, "...generally a Windows of SQL Server login" should be "generally a Windows or SQL Server login."
And in the paragraph immediately after Listing 10.2, I can not make sense of the opening statement, "That is all the code needed to set up the hold the data and provide access to it." The phrase before "and" is confusing. Please clarify.
July 29, 2015 at 7:13 am
Another great security article. Thanks.
July 29, 2015 at 7:44 am
Interesting. I recently had to implement row-level security on a reporting where access could be granted in three distinct ways.
Since all access to the reporting system is via stored procedures, I ended up writing an inline TVF similar to the security predicate example and CROSS APPLYing it in each of the stored procedures' SELECT statements.
July 29, 2015 at 11:52 am
williamn (7/29/2015)
In the first Tip, "...generally a Windows of SQL Server login" should be "generally a Windows or SQL Server login."
Thanks! I'll let the editor know.
williamn (7/29/2015)
And in the paragraph immediately after Listing 10.2, I can not make sense of the opening statement, "That is all the code needed to set up the hold the data and provide access to it." The phrase before "and" is confusing. Please clarify.
Sorry another typo that got by three of us! It should be, "That is all the code needed to set up to hold the data...." Although that is a bit awkward, so let's make it , "That is all the code needed to set up a table to hold the data...."
Thanks!
Don
July 30, 2015 at 3:31 pm
We use views for row level security (2008 R2) and found that you need to add "WITH CHECK OPTION" to the view or else users can insert data into the view for a "UserAccess" that is not theirs.
August 19, 2015 at 3:54 pm
I'd be interested in knowing if anyone is able to get this working via some front-end interface that sits between the database and somewhere else. Something that could interpret a custom user login and pass details from that through to the security function, but otherwise act normally once that authentication hits. That would be a great thing for SaaS businesses that want to enable MS tools at their place of business.
September 13, 2018 at 9:27 am
Great Article!!
Would you happen to know how I could build a script to determine if RLS is ON/OFF and to provide details?
Thank you in advance for all your help 🙂
Rudy
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply