Reports for the Integration Services Server
In the current release of SQL ServerIntegration Services, standard reports are available in SQL Server Management Studio to help you monitor Integration Services projects that have been deployed to the Integration Services server. These reports help you to view package status and history, and, if necessary, identify the cause of package execution failures.
At the top of each report page, the back icon takes you to the previous page you viewed, the refresh icon refreshes the information displayed on the page, and the print icon allows you to print the current page.
For information on how to deploy packages to the Integration Services server, see Deploy Projects to Integration Services Server.
Integration Services Dashboard
The Integration Services Dashboard report provides an overview of all the package executions on the SQL Server instance. For each package that has run on the server, the dashboard allows you to "zoom in" to find specific details on package execution errors that may have occurred.
The report displays the following sections of information.
| Section | Description |
|---|---|
| Execution Information | Shows the number of executions that are in different states (failed, running, succeeded, others) in the past 24 hours. |
| Package Information | Shows the total number of packages that have been executed in the past 24 hours. |
| Connection Information | Shows the connections that have been used in failed executions in the past 24 hours. |
| Package Detailed Information | Shows the details of the completed executions that have occurred in the past 24 hours. For example, this section shows the number of failed executions versus the total number of executions, the duration of an executions (in seconds), and the average duration of executions for over the past three months. You can view additional information for a package by clicking Overview, All Messages, and Execution Performance. The Execution Performance report shows the duration of the last execution instance, as well as the start and end times, and the environment that was applied. The chart and associated table included in the Execution Performance report shows the duration of the past 10 successful executions of the package. The table also shows the average execution duration over a three-month period. Different environments and different literal values may have been applied at runtime for these 10 successful executions of the package. Finally, the Execution Performance report shows the Active Time and Total Time for the package data flow components. The Active Time refers to the total amount of time that component has spent executing in all phases, and the Total Time refers to the total time elapsed for a component. The report only displays this information for package components when the logging level of the last package execution was set to Performance or Verbose. The Overview report shows the state of package tasks. The Messages report shows the event messages and error messages for the package and tasks, such as reporting the start and end times, and the number of rows written. You can also click View Messages in the Overview report to navigate to the Messages report. You can also click View Overview in the Messages report to navigate to the Overview report. |
You can filter the table displayed on any page by clicking Filter and then selecting criteria in the Filter Settings dialog. The filter criteria that are available depend on the data being displayed. You can change the sort order of the report by clicking the sort icon in the Filter Settings dialog.
All Executions Report
The All Executions Report displays a summary of all Integration Services executions that have been performed on the server. There can be multiple executions of the sample package. Unlike the Integration Services Dashboard report, you can configure the All Executions report to show executions that have started during a range of dates. The dates can span multiple days, months, or years.
The report displays the following sections of information.
| Section | Description |
|---|---|
| Filter | Shows the current filter applied to the report, such as the Start time range. |
| Execution Information | Shows the start time, end time, and duration for each package execution.You can view a list of the parameter values that were used with a package execution, such as values that were passed to a child package using the Execute Package task. To view the parameter list, click Overview. |
For more information about using the Execute Package task to make values available to a child package, see Execute Package Task.
For more information about parameters, see Integration Services (SSIS) Parameters.
All Connections
The All Connections report provides the following information for connections that have failed, for executions that have occurred on the SQL Server instance.
The report displays the following sections of information.
| Section | Description |
|---|---|
| Filter | Shows the current filter applied to the report, such as connections with a specified string and the Last failed time range. You set the Last failed time range to display only connection failures that occurred during a range of dates. The range can span multiple days, months, or years. |
| Details | Shows the connection string, number of executions during which a connection failed, and the date when the connection last failed. |
All Operations Report
The All Operations Report displays a summary of all Integration Services operations that have been performed on the server, including package deployment, validation, and execution, as well as other administrative operations. As with the Integration Services Dashboard, you can apply a filter to the table to narrow down the information displayed.
All Validations Report
The All Validations Report displays a summary of all Integration Services validations that have been performed on the server. The summary displays information for each validation such as status, start time, and end time. Each summary entry includes a link to messages generated during validation. As with the Integration Services Dashboard, you can apply a filter to the table to narrow down the information displayed.
Custom Reports
You can add a custom report (.rdl file) to the SSISDB catalog node under the Integration Services Catalogs node in SQL Server Management Studio. Before adding the report, confirm that you are using a three-part naming convention to fully qualify the objects you reference such as a source table. Otherwise, SQL Server Management Studio will display an error. The naming convention is <database>.<owner>.<object>. An example would be SSISDB.internal.executions.
Note
When you add custom reports to the SSISDB node under the Databases node, the SSISDB prefix is not necessary.
For instructions on how to create and add a custom report, see Add a Custom Report to Management Studio.
Related Tasks
View Reports for the Integration Services Server