* SSRS reports that operate over the SSIS catalog
* A stored proc, sp_ssiscatalog, that provides detailed analysis of the SSIS Catalog
SSIS Reporting Pack
for the documentation regarding the reports.
for documentation on that.
- These reports expose data from [SSISDB] hence you will need an instance of that database. See
Catalog Overview in SQL Server “Denali” CTP1 - SSIS for instructions on how to create [SSISDB]
- You will need a SQL Server Reporting Services Report Server onto which to deploy the reports. (Although, the installer provides a Visual Studio project for the reports so you
could just view them from there. I think it makes more sense to deploy them to a server though.)
- The installer does not (as yet) install the reports onto your Report Server, it only creates the requisite .rdl files on your machine. Hence, you will need the SQL Server 2012 development tools (aka SQL Server Data Tools aka SSDT), including the BI development
tools, in order to deploy the reports to your Report Server.
- Although not strictly a pre-requisite I highly recommend that you create an index on the [SSISDB].[internal].[event_messages].[operation_id] & [SSISDB].[internal].[operation_messages].[operation_id] fields. After using the reports in anger for a while
now I have come to realize that any sizeable data volumes in [SSISDB] will severely impact your ability to get any results quickly, particularly if those results use view [SSISDB].[catalog].[event_messages].
Phil Brammer has done the hard work for you and prepared some scripts to create the indexes that he recommends and he has shared them via his blog at
The installer (that you download from this site) will place the report .rdl files into a folder on your hard drive, by default this location is "C:\SSIS Reporting Pack" (you have the option to change this when you run the installer).
As well as the report files it also creates a file called SSISReportingPack.rptproj - this is a Reporting Services project that, when double-clicked, will open up in Visual Studio (assuming that you have the SQL Server 2012 development tools installed on your
machine). From there you will be able to deploy the reports in that report project just as you would any other report project.