This post is part of a series about SSIS Catalog Security. The other posts in this series are:
- One Way to Create an SSIS Catalog Read-Only Database Role
- One Way to Set SSIS Catalog Security
- SSIS Catalog Browser v0.9.9.3
I recently shared a post about the latest version of SSIS Catalog Browser, which plays nice(r) with SSIS Catalog security. My friend Bob shared that he has a lot of SSIS packages deployed in his enterprise. When we communicated about the SSIS Catalog Browser version, he lamented he also has a lot of SSIS Catalog Folders. Using the method I described in the post titled One Way to Set SSIS Catalog Security would be… cumbersome.
My suggestion is to create a database role – something I describe in my post titled One Way to Create an SSIS Catalog Read-Only Database Role – and then use that role in the following, cursor-y T-SQL script to assign read and read objects permissions to all SSIS Catalog Folders in an SSIS Catalog.
As always, I welcome your feedback, suggestions, thoughts, and concerns.