SSIS Catalog doesn't have option to give read access to SSIS Catalog to view package run reports - by Moni Sinha

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 700197 Comments
Status Closed Workarounds
Type Bug Repros 7
Opened 11/9/2011 5:22:09 PM
Access Restriction Public


Regarding Permissions to SSIS Catalog, here are the findings. We can give access in three ways

1.	READ Access – We can provide a user db_datareader access. With this the user can see the objects within the SSIS catalog database, but cannot see the reports.
2.	SSIS_ADMIN – Add the user to this database role in SSISDB. With this the user can view the reports. But it also provides them privileges to modify catalog information which is not expected. We can add it using below script 
EXEC sp_addrolemember 'ssis_admin' , 'REDMOND\PAIntelAnalyst'
3.	SYSADMIN - Add the user to this server role. This will make the user an admin on the SQL server. This is not intended.

Is there any method available which will have provision to give read only access to see SSIS Catalog package execution reports and not having modify Catalog access. 
Sign in to post a comment.
Posted by hoosierDevSQL on 5/19/2014 at 10:12 AM
The workaround does not allow access to the pre-canned reports only to the SSIS folder\project objects themselves, but not to the reports.
Posted by Koen Verbeeck on 9/5/2013 at 2:31 AM
When will this feature be included in the SISS catalog? SQL Server 2014?
Posted by Blaž Dakskobler on 11/18/2012 at 1:51 PM
This bug is still around - any chance you'll reevaluate your decision to not fix it?

Posted by Microsoft on 11/15/2011 at 9:55 AM
Hi Moni,

We’re closing this issue as “Won’t Fix.”

At this point the bug does not meet our bar for resolving prior to SQL Server 2012 RTM. As we approach the SQL Server 2012 release the bar for making code changes gets progressively higher.

As a workaround, you can develop your own custom reports that use the data in the SSISDB catalog database (specifically the views in the Catalog schema) that provide you with the data you need. As a starting point, you can use SQL Server Profiler to capture the queries used by the built-in reports, or you can use the community-developed reports already published on CodePlex:

Posted by Microsoft on 11/10/2011 at 9:29 AM
Thank you for your feedback! We are investigating the issue and will respond as soon as possible.