Database Reference
In-Depth Information
-- Return the execution ID
SELECT @exec_id
GO
The Integration Services job steps in SQL Server Agent have been enhanced in
SQL Server 2012 to support running packages stored in an SSIS Catalog. The user in-
terface is the same as when you run a package interactively through SSMS, and it
provides the same configuration options. Alternatively, you can run SSIS packages us-
ing the T-SQL job step. However, since this step does not support the use of proxy ac-
counts, you will be limited to running the packages as the SQL Server Agent service
account.
Parameters with DTEXEC
The command prompt utility to run SSIS packages (DTEXEC) has been updated to
support projects and parameters. DTEXEC is able to run packages stored within an
SSIS project file (
.ispac
) as well as start a server-based execution of a package
stored within an SSIS Catalog (local or remote). Both modes use different command-
line switches to set parameter values and are described in separate sections in the fol-
lowing pages.
Note
When working with individual SSIS package files (
.dtsx
), DTEXEC be-
haves the same as it did in previous versions of SQL Server. For more information on
the various command-line options for DTEXEC, see its entry in Books Online:
ht-
Projects on the File System
Although the new project deployment model is primarily meant to be used with the
SSIS Catalog, it is possible to run packages within a project file using DTEXEC. Pack-
ages run this way are executed locally by the DTEXEC process. Individual parameter
values can be set using the
/Set
option, and
/ConfigFile
can be used to set a
number of parameter values from a 2005/2008-style XML configuration file.
Table
Search WWH ::
Custom Search