May 1, 2013 at 6:10 am
I have inherited an SSIS package that has over a dozen Execute Package Task controls in it. They are all contained in one "master" package and that package is executed from a SQL Server Agent job. My question is this - Is there any reason or benefit to running each of these packages from an Execute Package Task control in one package rather than creating a step in the current Agent job for each package?
May 2, 2013 at 2:59 am
dfulks (5/1/2013)
I have inherited an SSIS package that has over a dozen Execute Package Task controls in it. They are all contained in one "master" package and that package is executed from a SQL Server Agent job. My question is this - Is there any reason or benefit to running each of these packages from an Execute Package Task control in one package rather than creating a step in the current Agent job for each package?
One reason might be that there is some sort of execution logic built into the package - including running order, degree of parallelism and conditional execution.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply