Using the dtexec utility, you can run packages that are stored in the file system, in an instance of SQL Server, or in the Integration Services Package Store. For information about the options that can be used in a dtexec command line, and some sample command lines, see dtexec Utility (SSIS Tool).

Note

On a 64-bit computer, Integration Services installs a 64-bit version of the dtexec utility. If you have to run certain packages in 32-bit mode, you will have to install the 32-bit version of the dtexec utility. To install the 32-bit version of the dtexec utility, you must select either Client Tools or Business Intelligence Development Studio during setup.

To run a package by using the dtexec utility

At the command prompt, type dtexec / followed by the DTS, SQL, or File option and the package path. Make sure to include the package file name in the package path.

If the package encryption level is EncryptSensitiveWithPassword or EncryptAllWithPassword, use the Decrypt option to provide the password. If you do not inlude a password, dtexec will prompt you for the password.

The Execute Package Utility (dtexecui.exe) creates a command line that you can use in the following ways:

Copy to a file and use with the CommandFile option of the dtexec utility.

Paste directly in the Command Prompt window when you use the dtexec utility to run a package.

The Execute Package Utility is available only in a 32-bit version. On a 64-bit computer, any commands that the Execute Package Utility creates should also be tested in 64-bit mode before you deploy or schedule them on a production server. To test these commands in 64-bit mode, use the 64-bit version of the dtexec utility.

To run a package by using the Execute Package Utility

In Management Studio, on the View menu, click Object Explorer.

In Object Explorer, click Connect, and then click Integration Services.

When you create a SQL Server Agent job to run packages, you must create a separate step for each package that you want to run. The job can be associated with one or more schedules, or can be an unscheduled job that you run manually.

If the source is SQL Server or the SSIS Package Store, provide the server name and select the authentication mode to use. Then, provide the name of the package, or click the ellipsis button (…) and locate the package.

If the source is the file system, provide the path and name of the package, or click the ellipsis button (…) and locate the package.

Important

For password-protected SSIS packages, click the Configurations tab to enter the password in the Package Password dialog box. Otherwise, the SQL Server Agent job that runs the password-protected package will fail.

To specify command-line options, do the following:

Click the Command Files tab to specify the files that contain the options that the package uses.

Click the Command Line tab to modify or restore the command-line options.

Click the Execution Options tab to specify the package run-time behavior, such as whether the package fails if warnings occur.

Click the Logging tab to add log providers. Select a log provider in the Log Provider list and then type the connection string.

Click the Set Values tab to map properties and variables to values.

Note

The property path uses this syntax: \Package\<container name>.<property name>. Depending on the package structure, a container might include other containers, in which case nested containers are separated by a back slash (\). For example, Package\MyForeachLoop\MySequence\MyExecuteSQLTask.Description.

Click the Verification tab to specify whether only signed packages can run and to specify the version of package to run.