Sequence Containers
Sequence Containers
handle the flow of a subset of a package and can help you divide a package
into smaller, more
manageable pieces. Some nice applications that you can use sequence containers
for include the
following:
- Grouping tasks so that you can disable a part of the package that ’ s no longer needed Narrowing the scope of the variable to a container
- Managing the properties of multiple tasks in one step by setting the properties of the Container
- Using one method to ensure that multiple tasks have to execute successfully before the next task executes
- Creating a transaction across a series of data - related tasks, but not on the entire package
- Creating event handlers on a single container, wherein you could send an email if anything
- Inside one container fails and perhaps page if anything else fails
Sequence containers
show up like any other task in your Control Flow tab. Once you drag and drop
any
container from your
Toolbox onto the design pane, you just have to drag the tasks you ’ d like to
use into
the container.
A container can be
considered to be a miniature package. Inside the container, all task names must
be
unique, just like
from within a package where there are no containers.
You also cannot
connect a task in one container to anything outside of the container. If you
try to do this,
you will receive
the following error:
Cannot create
connector.
Cannot connect
executable from different containers.
Containers such as
the Sequence Container can also be embedded in each other. As a best practice
each
of your SSIS
packages should contain a series of containers to help organize the package and
to make it
easy to disable
subject areas quickly. Each set of tables that you must load probably fits into
a subject
area, such as
Accounting or HR. Each of these loads should be placed in its own Sequence
Container.
Additionally, you
may want to create a Sequence Container for the preparation and cleanup stages
of
your package.
No comments:
Post a Comment