Export (0) Print
Expand All

Run Integration Services (SSIS) Packages


Applies To: SQL Server 2016

To run an Integration Services package, you can use one of several tools depending on where those packages are stored. The tools are listed in the table below.

To store a package on the Integration Services server, you use the project deployment model to deploy the project to the server. For information, see Deploy Projects to Integration Services Server.

To store a package in the SSIS Package store, the msdb database, or in the file system, you use the package deployment model. For more information, see Legacy Package Deployment (SSIS).

ToolPackages that are stored on the Integration Services serverPackages that are stored in the SSIS Package Store or in the msdb databasePackages that are stored in the file system, outside of the location that is part of the SSIS Package Store
SQL Server Data ToolsNoNo

However, you can add an existing package to a project from the SSIS Package Store, which includes the msdb database. Adding an existing package to the project in this manner makes a local copy of the package in the file system.
SQL Server Management Studio, when you are connected to an instance of the Database Engine that hosts the Integration Services server

For more information, see Execute Package Dialog Box

However, you can import a package to the server from these locations.

However, you can import a package to the server from the file system.
SQL Server Management Studio, when it is connected to the Integration Services service that manages the SSIS Package StoreNoYesNo

However, you can import a package to the SSIS Package Store from the file system.

For more information, see dtexec Utility.

For more information, see Execute Package Utility (DtExecUI) UI Reference
SQL Server Agent

You use a SQL Server Agent job To schedule a package.

For more information, see SQL Server Agent Jobs for Packages.
Built-in stored procedure

For more information, see catalog.start_execution (SSISDB Database)
Managed API, by using types and members in the Microsoft.SqlServer.Management.IntegrationServices namespaceYesNoNo
Managed API, by using types and members in the Microsoft.SqlServer.Dts.Runtime namespaceNot currentlyYesYes

Integration Services packages can be enabled for logging and you can capture run-time information in log files. For more information, see Integration Services (SSIS) Logging.

You can monitor Integration Services packages that are deployed to and run on the Integration Services server by using operation reports. The reports are available in SQL Server Management Studio. For more information, see Reports for the Integration Services Server.

dtexec Utility
SQL Server Import and Export Wizard

Community Additions

© 2016 Microsoft