Precedence constrains in a master package issue
-
I am running into an interesting problem with precedence constraints:
I have a set up with master package that executes 4 children packages. I am doing this because I have a parent table load that needs to execute first before children tables can be loaded (with foreign key relationships).The problem that I seem to be experiencing is that my child package seems to be starting before the parent package is completed and as a result doesn't load anything as it didn't find any parent values in the parent table. Is there something more to the precedence constraint that I need to be doing (possible expressions on sessionId ) other than constraint:Success? My concerns is that SSIS is receiving a message that that parent package (first in sequence) is complete even thought data has not been committed yet. I am loading decent amount of data - about 14 million to the parent (first) table and 90 million to the child table.
-
Try putting your parent package in a Sequence container and connecting the child packages to that.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin -
Check the "ExecuteOutOfProcess" property, which controls parallelism. I found a reference in this blog: https://blog.sqlauthority.com/2015/02/12/sql-server-the-basics-of-the-execute-package-task-notes-from-the-field-067/
It doesn't specifically state, but I suspect that if Out Of Process is true, the running package spawns off the new package in its own thread and doesn't wait for completion before moving on to the next step. -
I've tried the sequence container and that didn't help. ExecuteOutOfProcess is set to false.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply