| title | description | author | ms.author | ms.date | ms.service | ms.subservice | ms.topic | f1_keywords | helpviewer_keywords | |||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Sequence Container |
Sequence Container |
chugugrace |
chugu |
03/01/2017 |
sql |
integration-services |
conceptual |
|
|
[!INCLUDEsqlserver-ssis]
The Sequence container defines a control flow that is a subset of the package control flow. Sequence containers group the package into multiple separate control flows, each containing one or more tasks and containers that run within the overall package control flow.
The Sequence container can include multiple tasks in addition to other containers. Adding tasks and containers to a Sequence container is similar to adding them to a package, except you drag the tasks and containers to the Sequence container instead of to the package container. If the Sequence container includes more than one task or container, you can connect them using precedence constraints just as you do in a package. For more information, see Precedence Constraints.
There are many benefits of using a Sequence container:
-
Disabling groups of tasks to focus package debugging on one subset of the package control flow.
-
Managing properties on multiple tasks in one location by setting properties on a Sequence container instead of on the individual tasks.
For example, you can set the Disable property of the Sequence container to True to disable all the tasks and containers in the Sequence container.
-
Providing scope for variables that a group of related tasks and containers use.
-
Grouping many tasks so you can more easily managed them by collapsing and expanding the Sequence container.
You can also create task groups, which expand and collapse using the Group box. However, the Group box is a design-time feature that has no properties or run-time behavior. For more information, see Group or Ungroup Components
-
Set a transaction attribute on the Sequence container to define a transaction for a subset of the package control flow. In this way, you can manage transactions at a more granular level.
For example, if a Sequence container includes two related tasks, one task that deletes data in a table and another task that inserts data into a table, you can configure a transaction to ensure that the delete action is rolled back if the insert action fails. For more information, see Integration Services Transactions.
The Sequence container has no custom user interface and you can configure it only in the Properties window of [!INCLUDEssBIDevStudioFull] or programmatically.
For information about programmatically setting these properties, see documentation for the T:Microsoft.SqlServer.Dts.Runtime.Sequence class in the Developer Guide.
For information about how to set properties of the component in the [!INCLUDEssBIDevStudioFull], see Set the Properties of a Task or Container.
Add or Delete a Task or a Container in a Control Flow
Connect Tasks and Containers by Using a Default Precedence Constraint
Integration Services Containers