Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Sequence Containers ISSUE

Status
Not open for further replies.

MDXer

Technical User
Oct 19, 2002
1,982
US
Background:

Process is ETL for a data warehouse. Design is multiple SSIS packages, 1 package per process task (ie Package for Patron Dimension load, package for Fact table load etc). I control the execution and order of execution, obviously dimensions process prior to fact tables, through a Master Load package. Within this package I have a number of Steps that we will call pre-execution, such as email notification the process has begun and logging. I then have Sequence Containers for like process types these containers hold the execute package tasks for the packages that run each process. The packages finishes with some post process tasks such as A script to generate either a sucess or failure email. and the sending of the email and update of the log entry.

The issue arises that when a Execute Package Task Completes seperately the Container is the Set to a Status of Success rather than stil in process. What then happens is that the Post execute processes are fired upon the completion of each Execute package Task.

Has anyone experienced this issue and found a way to control it?

Paul
---------------------------------------
Shoot Me! Shoot Me NOW!!!
- Daffy Duck
 
Ok I figured this one out.

I guess one detail I left out was since this is a sizeable DW and ETL process where we have all types of Audit logging and Notifications happening I created a template SSIS package to ensure that the Variables and Process flow was consistent across all packages.

This Template package raises the issue that I was encountering. Which is that by using a template all Object IDs for the various common tasks were the same across all packages so when it came time to execute Status Mail Success in the Child package since it had the the same GUID reference as the parent it actually executed the Mail Task in both packages.

Which leads me to ask the question. What good is creating a template then.

Be warned that this holds true for the Package ID, however you can generate a new Package ID just not task IDs.

Paul
---------------------------------------
Shoot Me! Shoot Me NOW!!!
- Daffy Duck
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top