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.
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.
Providing scope for variables that a group of related tasks and containers use.
You can 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 Ensuring Data Integrity by Using Transactions.
The Sequence container has no custom user interface and you can configure it only in the Properties window of Business Intelligence Development Studio or programmatically.
For more information about setting these properties in the Business Intelligence Development Studio, see How to: Set the Properties of a Task or Container.
Configuring the Sequence Container Programmatically
For more information about programmatically setting these properties, see Sequence.