This topic has not yet been rated - Rate this topic

Execute Package Utility (General Page)

SQL Server 2008 R2

Use the General page of the Execute Package Utility dialog box to specify a package name and location.

The Execute Package utility (dtexecui.exe) always runs a package on the local computer, even if the package is saved on a remote server. If the remote package uses configuration files that also are saved on the remote server, then the Execute Package utility may not locate the configurations and the package fails. To avoid this problem, the configurations must be referenced by using a Universal Naming Convention (UNC) share name like \\myserver\myfile.

Static Options

Package source

Specify the location of the package to run, using the following options:

Value	Description
SQL Server	Select this option when the package resides in Microsoft SQL Server. Specify an instance of SQL Server and provide a user name and password for SQL Server Authentication. Each user name and password adds the /USER username and /PASSWORD password options to the command prompt.
File system	Select this option when the package resides in the file system.
SSIS Package Store	Select this option when the package resides in the SSIS Package Store.

Each of these selections has the following set of options.

Execute

Click to run the package.

Close

Click to close the Execute Package Utility dialog box.

Dynamic Options

Package Source = SQL Server

Server

Type the name of the server where the package resides, or select a server from the list.

Log on to the server

Specify whether the package should use Windows Authentication or SQL Server Authentication to connect to SQL Server. Windows Authentication is recommended for better security. With Windows Authentication you do not have to specify a user name and password.

Use Windows Authentication

Select this option to use Windows Authentication and log on using a Microsoft Windows user account.

Use SQL Server Authentication

Select this option to use SQL Server Authentication. When a user connects with a specified login name and password from a non-trusted connection, SQL Server performs the authentication by checking to see if a SQL Server login account has been set up and if the specified password matches the one previously recorded. If SQL Server cannot find the login account, authentication fails, and the user receives an error message.

Important
When possible, use Windows Authentication.

Package

Type the name of the package, or click the ellipsis button (…) to locate a package using the Select an SSIS Package dialog box.

Package Source = File System

Package: Type the name of the package, or click the ellipsis button (…) to locate a package using the Open dialog box. By default, the dialog box lists only files that have the .dtsx extension.

Package Source = SSIS Package Store

Server

Type the name of the computer where the package resides, or select a computer from the list.

Log on to the server

Specify whether the package should use Microsoft Windows Authentication to connect to the package source. Windows Authentication is recommended for better security. With Windows Authentication you do not have to specify a user name and password.

Use Windows Authentication: Select this option to use Windows Authentication and log on using a Microsoft Windows user account.
Use SQL Server Authentication: This option is not available when you run a package stored in the SSIS Package Store.

Package

Type the name of the package, or click the ellipsis button (…) to locate a package using the Select an SSIS Package dialog box.

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)

Community Additions

ADD

Execute Package Utility (General Page)

Package Source = SQL Server

Package Source = File System

Package Source = SSIS Package Store

Tasks

Reference

Concepts

Community Additions