SSIS Parent/Child Package error propagation
I have a somewhat complex question about error messages propgating from child to parent packages. This is all in SSIS 2005, but if there's a 2008 solution that would be dandy. We have a three-layered ETL structure, where each call to a package is executed by an intermediate "metadata" package which handles logging, error handling, DQ, etc. and also calls the actual ETL package. Executing this ETL would look something like this: Call metadata package with "Master" parameter Metadata package does logging etc., calls Master Package Master package calls metadata package with "Extract Layer" parameter Metadata package does logging etc., calls Extract Layer package Extract Layer package calls metadata package with "ETL Extract Job 1" parameter Metadata package does logging etc., calls ETL Extract Job 1 package ETL Extract Job 1 package runs, completes (Repeat steps 5-7 for each extract package) (Repeat steps 3-7 for each layer package) The idea is that if an error happens in a package, that error will propagate up to the metadata package which called it, get handled there, and propagate no further . (If an error happens in the metadata package, it should get handled within that package.) I know that the Propagate system variable is ignored for errors passing from child to parent packages. Since we want the error to propagate up to the metadata package, setting DisableEventHandlers on the Execute Package task in the metadata package doesn't do what we want either. What we would like is either to be able to stop an error from propagating past a certain point, or to identify that an error has done so (so if the metadata package sees an error that has already gone through at least one other metadata package, it just ignores it). I've seen descriptions of System::ParentContainerGUID and System::SourceParentGUID, but it doesn't seem like they would do the trick (they only tell you about the immediate parent container, and apparently they don't work across packages). Is there some other technique to use?
June 16th, 2010 9:49pm

I have a hard time trying to propagate an error from child package to parent. In my child package I have a script that sets the final response as "Failure", so causing an error. The parent calls this package, then has two arrows (you know, green and red). The green arrow always works, the red one not. The parent doesn't catch the error result from the child. It seemed to me that this is somewhat related with GSpeare more complex structure about error propagation. How can I propagate the error from the child to parent?
Free Windows Admin Tool Kit Click here and download it now
July 1st, 2011 2:11pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics