Execution of Projects and Packages

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 Package Deployment (SSIS).

Tool	Packages that are stored on the Integration Services server	Packages that are stored in the SSIS Package Store or in the msdb database	Packages that are stored in the file system, outside of the location that is part of the SSIS Package Store
SQL Server Data Tools	No	No 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.	Yes
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	Yes	No However, you can import a package to the server from these locations.	No 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 Store	No	Yes	No However, you can import a package to the SSIS Package Store from the file system.
dtexec For more information, see dtexec Utility.	Yes	Yes	Yes
dtexecui For more information, see Execute Package Utility (DtExecUI) UI Reference	No	Yes	Yes
SQL Server Agent You use a SQL Server Agent job To schedule a package. For more information, see SQL Server Agent Jobs for Packages.	Yes	Yes	Yes
Built-in stored procedure For more information, see catalog.start_execution (SSISDB Database)	Yes	No	No
Managed API, by using types and members in the Microsoft.SqlServer.Management.IntegrationServices namespace	Yes	No	No
Managed API, by using types and members in the Microsoft.SqlServer.Dts.Runtime namespace	Not currently	Yes	Yes

Execution and Logging

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 Operations Reports for the Integration Services Server.

Related Tasks

• Schedule a Package by using SQL Server Agent

• Run a Package in SQL Server Data Tools

• Run a Package on the SSIS Server Using SQL Server Management Studio

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: Visit the Integration Services page on MSDN For automatic notification of these updates, subscribe to the RSS feeds available on the page.

See Also

Tasks

SQL Server Import and Export Wizard

Concepts

dtexec Utility