Stairway to SQL Server Security Level 4: Permissions

  • Comments posted to this topic are about the item Stairway to SQL Server Security Level 4: Permissions

  • We've had good success lumping similarly used tables and procedures into schemas and then creating a role for the schema and assigning "User" permissions to the role, specifically SELECT, INSERT, UPDATE, DELETE, EXECUTE. For more limited use, we'd also create the schema read only role, which only had access to SELECT.

    Your definitions were spot-on for assignment but it may be more difficult to maintain with multiple roles.

  • Thanks! Yes, and I talk about schemas and security in Level 5. And yes about multiple roles.

    Keeping it simple goes a long way in keeping things secure.


  • Very helpful to me today as I had a user who couldn't refresh a SharePoint SS due to a lack of access to the new view I had created. Thanks.

Viewing 4 posts - 1 through 3 (of 3 total)

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