Using Variables in Packages
Variables are a useful and flexible addition to SQL Server 2005 Integration Services (SSIS) packages; they can provide communication among objects in the package, and between parent and child packages. Variables can also be used in expressions and scripts.
User-Defined Variables and System Variables
Integration Services provides system variables and supports user-defined variables. When you create a new package, add a container or a task to a package, or create an event handler, Integration Services includes a set of system variables for the container. System variables contain useful information about a package, container, task, or event handler. For example, at run time the MachineName system variable contains the name of the computer on which the package is running and StartTime the time the package started to run. System variables are read-only. For more information, see System Variables.
You can create user-defined variables and then use them in packages. User-defined variables can be used in many ways in SSIS: in scripts; in the expressions used by precedence constraints, the For Loop container, the Derived Column transformation, and the Conditional Split transformation; and in the property expressions that update property values.
For example, you can use a user-defined variable in the evaluation condition for the For Loop container. You can also map the enumerator collection value in a Foreach Loop container to a variable, and if an Execute SQL task uses a parameterized SQL statement, you can map the parameters for the statement to variables. For more information, see Integration Services Variables.
Variables Usage Scenarios
Variables are used in many different ways in Integration Services packages. You will probably find that package development does not progress far before you have to add a user-defined variable to your package to implement the flexibility and manageability your solution requires. Depending on the scenario, system variables are also commonly used.
Property Expressions Use variables to provide values in the property expressions that set the properties of packages and package objects. For example, the expression,
SELECT * FROM @varTableName includes the variable
varTableName that updates the SQL statement that an Execute SQL task runs. The expression,
DATEPART("d", GETDATE()) == 1? @[User::varPackageFirst]:@[User::varPackageOther]", updates the package that the Execute Package task runs, by running the package specified in the
varPackageFirst variable on the first day of the month and running the package specified in the
varPackageOther variable on other days. For more information, see Using Property Expressions in Packages.
Data Flow Expressions Use variables to provide values in the expressions that the Derived Column and Conditional Split transformations use to populate columns, or to direct data rows to different transformation outputs. For example, the expression,
@varSalutation + LastName, concatenates the value in the
VarSalutation variable and the
LastName column. The expression,
Income < @HighIncome, directs data rows in which the value of the
Income column is less than the value in the
HighIncome variable to an output. For more information, see Derived Column Transformation, Conditional Split Transformation, and Using Expressions in Packages.
Precedence Constraint Expressions Provide values to use in precedence constraints to determine whether a constrained executable runs. The expressions can be used either together with an execution outcome (success, failure, completion), or instead of an execution outcome. For example, if the expression,
@varMax > @varMin, evaluates to true, the executable runs. For more information, see Adding Expressions to Precedence Constraints.
Parameters and Return Codes Provide values to input parameters, or store the values of output parameters and return codes. You do this by mapping the variables to parameters and return values. For example, if you set the variable
varProductId to 23 and run the SQL statement,
SELECT * from Production.Product WHERE ProductID = ?, the query retrieves the product with a
ProductID of 23. For more information, see Execute SQL Task.
For Loop Expressions Provide values to use in the initialization, evaluation, and assignment expressions of the For Loop. For example, if the variable
varCount is 2 and
varMaxCount is 10, the initialization expression is
@varCount, the evaluation expression is
@varCount < @varMaxCount, and the assignment expression is
@varCount =@varCount +1, then the loop repeats 8 times. For more information, see For Loop Container.
Parent Package Variable Configurations Pass values from parent packages to child packages. Child packages can access variables in the parent package by using parent package variable configurations. For example, if the child package must use the same date as the parent package, the child package can define a parent package variable configuration that specifies a variable set by the GETDATE function in the parent package. For more information, see Execute Package Task and Package Configurations.
Script Task and Script Component Provide a list of read-only and read/write variable to the Script task or Script component, update the read/write variables within the script, and then use the updated values in or outside the script. For example, in the code,
numberOfCars = CType(Dts.Variables("NumberOfCars").Value, Integer), the script variable
numberOfCars is updated by the value in the variable,
NumberOfCars. For more information, see Using Variables in the Script Task.
Configurations and Variables
To dynamically update variables, you can create configurations for the variables, deploy the configurations with the package, and then update the variable values in the configuration file when you deploy the packages. At run time, the package uses the updated variable values. For more information, see Creating Package Configurations.
To add, modify, and delete user-defined variables
Help and Information
14 April 2006