This project is read-only.

Project Description

This project used to consist solely of a suite of reports that operated over the SSIS Catalog (hence the URL,

Over time it has been expanded to include

  • A stored proc, usp_ssiscatalog, that provides detailed analysis of the SSIS Catalog
  • Restart Framework, a collection of SSIS packages and database objects that provide restartability for your SSIS executions and in doing so fill a gaping hole in SSIS as it is today.

Go to SSIS Reporting Pack for the documentation regarding the reports.
Go to usp_ssiscatalog for documentation on stored procedure usp_ssiscatalog.
Go to Restart Framework for documentation on that.

Installation Overview

A single installer provides both the SSRS Reports and the .dacpac file that can be used to deploy usp_ssiscatalog. The installer only places the requisite files onto your hard drive, there are additional steps thereafter.


  • 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 (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 BI development tools (referred to as SSDT-BI), in order to deploy the reports to your Report Server.
  • Likewise the installer also does not create usp_ssiscatalog in a database for you. Instead it provides you a dacpac file that you can then use to create usp_ssiscatalog (and all its dependencies) in whatever database you wish to.
  • 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

Installation Steps


The installer will place the report .rdl files into a folder on your hard drive, by default this location is "C:\SSIS Reporting Pack\Reports" (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.


The installer will place two dacpac files into a folder on your hard drive, by default this location is "C:\SSIS Reporting Pack\Dacpacs" (you have the option to change this when you run the installer). The steps to follow thereafter are documented at Installation Instructions.

Support SSIS Reporting Pack & sp_ssicatalog

SSIS Reporting Pack & usp_ssicatalog are provided totally, utterly and sincerely free-of-charge. Nonetheless, contributions to help ensure future maintenance and enhancements and/or beer money would be much appreciated. You can contribute via PayPal by going to

Last edited Apr 12, 2014 at 10:38 PM by jamiet, version 56