Export (0) Print
Expand All

Viewing and Stopping Packages Running on the Integration Services Server

The SSISDB database stores execution history in internal tables that are not visible to users. However it exposes the information that you need through public views that you can query. It also provides stored procedures that you can call to perform common tasks related to packages.

Typically you manage Integration Services objects on the server in SQL Server Management Studio. However you can also query the database views and call the stored procedures directly, or write custom code that calls the managed API. SQL Server Management Studio and the managed API query the views and call the stored procedures to perform many of their tasks. For example, you can view the list of Integration Services packages that are currently running on the server, and request packages to stop if you have to.

You can view the list of packages that are currently running on the server in the Active Operations dialog box. For more information, see Active Operations Dialog Box.

For information about the other methods that you can use to view the list of running packages, see the following topics.

Transact-SQL access

To view the list of packages that are running on the server, query the view, catalog.executions (SSISDB Database) for packages that have a status of 2.

Programmatic access through the managed API

See the [Microsoft.SqlServer.Management.IntegrationServices] namespace and its classes.

You can request a running package to stop in the Active Operations dialog box. For more information, see Active Operations Dialog Box.

For information about the other methods that you can use to stop a running package, see the following topics.

Transact-SQL access

To stop a package that is running on the server, call the stored procedure, catalog.stop_operation (SSISDB Database).

Programmatic access through the managed API

See the [Microsoft.SqlServer.Management.IntegrationServices] namespace and its classes.

To view the history of packages that have run in Management Studio, use the All Executions report. For more information on the All Executions report and other standard reports, see Reports for the Integration Services Server.

For information about the other methods that you can use to view the history of running packages, see the following topics.

Transact-SQL access

To view information about packages that have run, query the view, catalog.executions (SSISDB Database).

Programmatic access through the managed API

See the [Microsoft.SqlServer.Management.IntegrationServices] namespace and its classes.

Integration Services icon (small)  Stay Up to Date with Integration Services

For the latest downloads, articles, samples, and videos from Microsoft, as well as selected solutions from the community, visit the Integration Services page on MSDN:


For automatic notification of these updates, subscribe to the RSS feeds available on the page.

Community Additions

ADD
Show:
© 2014 Microsoft