Executing Multiple "Execute Package Tasks" in a single Execute Package Package

Question

Executing Multiple "Execute Package Tasks" in a single Execute Package Package

Howard C. BAchtel-438731

SSCrazy

Points: 2384
More actions
November 26, 2013 at 2:05 pm

#286865

I have a set (curently 10) individual packages that put the same data filtered for different sites. I have created a "Master" package made up of 10 "Execute Package Tasks" with each individual package to be executed by the execution of the single package.
This is currently in development mode for testing of the concept of executing multiple package tasks within one package. When I execute the "Master" package, the first of the individual packages runs and the full process stops after completion of the first one because in development mode when a single package completes all SSIS processes stop until manually cleared from debugging mode.
Is there a way to test the full process of executing the full 10 packages from a single package?
Thanks in advance.

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Koen Verbeeck SSC Guru Points: 259105 More actions · Answer 1

Can you post a screenshot? Normally all packages should run in parallel when executed from the master package.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

Howard C. BAchtel-438731 SSCrazy Points: 2384 More actions · Answer 2

Thanks. I think you may have given me the solution with your question. I had the packages running in serial vs. parallel. I will change that and if it does not work I will send the screen shot as requested. It makes sense to me and I just never thought of it.

I appreciate your thought.

Phil Parkin SSC Guru Points: 246959 More actions · Answer 3

Koen Verbeeck (11/26/2013)
Can you post a screenshot? Normally all packages should run in parallel when executed from the master package.

You should bear in mind what the packages are doing when thinking of running in parallel. If they are all updating the same destination table (for example), parallelism may just lead to blocking.

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

Koen Verbeeck SSC Guru Points: 259105 More actions · Answer 4

Phil Parkin (11/27/2013)
Koen Verbeeck (11/26/2013)
Can you post a screenshot? Normally all packages should run in parallel when executed from the master package.
You should bear in mind what the packages are doing when thinking of running in parallel. If they are all updating the same destination table (for example), parallelism may just lead to blocking.

I just said if there are no precedence constraints, packages run in parellel.

I didn't say they run in parallel efficiently 😀 😉

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

Phil Parkin SSC Guru Points: 246959 More actions · Answer 5

Koen Verbeeck (11/27/2013)
Phil Parkin (11/27/2013)
Koen Verbeeck (11/26/2013)
Can you post a screenshot? Normally all packages should run in parallel when executed from the master package.
You should bear in mind what the packages are doing when thinking of running in parallel. If they are all updating the same destination table (for example), parallelism may just lead to blocking.
I just said if there are no precedence constraints, packages run in parellel.
I didn't say they run in parallel efficiently 😀 😉

Well, you used the word 'should' rather than 'would'. That sounds to me like you are giving advice 🙂

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

Koen Verbeeck SSC Guru Points: 259105 More actions · Answer 6

Phil Parkin (11/27/2013)
Koen Verbeeck (11/27/2013)
Phil Parkin (11/27/2013)
Koen Verbeeck (11/26/2013)
Can you post a screenshot? Normally all packages should run in parallel when executed from the master package.
You should bear in mind what the packages are doing when thinking of running in parallel. If they are all updating the same destination table (for example), parallelism may just lead to blocking.
I just said if there are no precedence constraints, packages run in parellel.
I didn't say they run in parallel efficiently 😀 😉
Well, you used the word 'should' rather than 'would'. That sounds to me like you are giving advice 🙂

Yes, should as in "When there are no precedence constraints, the packages should run in parallel. If they don't, something is wrong."

But I get where you're getting at.

Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP

Howard C. BAchtel-438731 SSCrazy Points: 2384 More actions · Answer 7

Thanks to all. I modified to run in parallel and all is well. As informtion, the individual packages are the same at the source (SQL Server tables with information for all destinations) and the reason for the different packages is the destination (all different) with parameter queries to determine the destination.