Integration Services Containers
Containers are objects in SQL Server 2005 Integration Services (SSIS) that provide structure to packages and services to tasks. They support repeating control flows in packages, and they group tasks and containers into meaningful units of work. Containers can include other containers in addition to tasks.
Packages use containers for the following purposes:
- Repeat tasks for each element in a collection, such as files in a folder, schemas, or SQL Server Management Objects (SMO) objects. For example, a package can run Transact-SQL statements that reside in multiple files.
- Repeat tasks until a specified expression evaluates to false. For example, a package can send a different e-mail message seven times, one time for every day of the week.
- Group tasks and containers that must succeed or fail as a unit. For example, a package can group tasks that delete and add rows in a database table, and then commit or roll back all the tasks when one fails.
Container Types
Integration Services provides four types of containers for building packages. The following table lists the container types.
| Container | Description |
|---|---|
Runs a control flow repeatedly by using an enumerator. |
|
Runs a control flow repeatedly by testing a condition. |
|
Groups tasks and containers into control flows that are subsets of the package control flow. |
|
Provides services to a single task. |
Packages and events handlers are also types of containers. For information see Integration Services Packages and Integration Services Event Handlers.
Summary of Container Properties
All container types have a set of properties in common. If you create packages using the graphical tools that Integration Services provides, the Properties window lists the following properties for the Foreach Loop, For Loop, and Sequence containers. The task host container properties are configured as part of configuring the task that the task host encapsulates. You set the Task Host properties when you configure the task.
| Property | Description |
|---|---|
DelayValidation |
Indicates whether validation of the container is delayed until run time. The property contains a Boolean, and its value is False. |
Description |
The container description. The property contains a string, but may be blank. |
Disable |
Indicates whether the container runs. The property contains a Boolean, and its default value is False. |
DisableEventHandlers |
Indicates whether the event handlers associated with the container run. The property contains a Boolean, and its default value is False. |
FailPackageOnFailure |
Specifies whether the package fails if an error occurs in the container. The property contains a Boolean, and its default value is False. |
FailParentOnFailure |
Specifies whether the parent container fails if an error occurs in the container. The property contains a Boolean, and its default value is False. |
ForcedExecutionValue |
If ForceExecutionValue is set to True, a value that specifies the execution value that the container returns. The default value of this property is 0. |
ForcedExecutionValueType |
The data type of ForcedExecutionValue. |
ForceExecutionResult |
Specifies whether the execution value of the container is forced. The property contains a Boolean, and its default value is False. |
ForceExecutionValue |
The execution result of the container. The values are None, Success, Failure, and Completion. The default value of this property is None. For more information, see T:Microsoft.SqlServer.Dts.Runtime.DTSForcedExecResult. |
ID |
The container GUID, which is assigned when the package is created. This property is read-only. |
IsolationLevel |
The isolation level of the container transaction. The values are Unspecified, Chaos, ReadUncommitted, ReadCommitted, RepeatableRead, Serializable, and Snapshot. The default value of this property is Serializable. For more information, see IsolationLevel. |
LocaleID |
A Microsoft Win32 locale. The default value of this property is the locale of the operating system on the local computer. |
LoggingMode |
A value that specifies the logging behavior of the container. The values are Disabled, Enabled, and UseParentSetting. The default value of this property is UseParentSetting. For more information, see DTSLoggingMode. |
MaximumErrorCount |
The maximum number of errors that can occur before a container stops running. The default value of this property is 1. |
Name |
The name of the container. |
TransactionOption |
The transactional participation of the container. The values are NotSupported, Supported, Required. The default value of this property is Supported. For more information, see DTSTransactionOption. |
To learn about all the properties that are available to Foreach Loop, For Loop, Sequence, and Task Host containers when configure them programmatically, see the following Integration Services API topics:
Objects that Extend Container Functionality
Containers include control flows that consist of executables and precedence constraints, and may use event handlers, and variables. The task host container is an exception: because the task host container encapsulates a single task, it does not use precedence constraints.
Executables
Executables refers to the container-level tasks and any containers within the container. An executable can be one of the tasks and containers that Integration Services provides or a custom task. For more information, see Integration Services Tasks and Integration Services Containers.
Precedence Constraints
Precedence constraints link containers and tasks within the same parent container into an ordered control flow. For more information, see Precedence Constraints.
Event Handlers
Event handlers at the container level respond to events raised by the container or the objects it includes. For more information, see Integration Services Event Handlers.
Variables
Variables that are used in containers include the container-level system variables that Integration Services provides and the user-defined variables that the container uses. For more information, see Integration Services Variables.
See Also
Concepts
Help and Information
Getting SQL Server 2005 Assistance
Change History
| Release | History |
|---|---|
14 April 2006 |
|