Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Executing Multiple "Execute Package Tasks" in a single Execute Package Package Expand / Collapse
Author
Message
Posted Tuesday, November 26, 2013 2:05 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Yesterday @ 7:00 AM
Points: 85, Visits: 336
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.
Post #1517824
Posted Tuesday, November 26, 2013 3:00 PM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 3:27 PM
Points: 12,185, Visits: 9,134
Can you post a screenshot? Normally all packages should run in parallel when executed from the master package.



How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1517840
Posted Tuesday, November 26, 2013 6:36 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Yesterday @ 7:00 AM
Points: 85, Visits: 336
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.
Post #1517861
Posted Wednesday, November 27, 2013 3:16 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 1:50 PM
Points: 4,828, Visits: 11,179
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.



Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.
Post #1517963
Posted Wednesday, November 27, 2013 3:20 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 3:27 PM
Points: 12,185, Visits: 9,134
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




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1517966
Posted Wednesday, November 27, 2013 3:29 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Today @ 1:50 PM
Points: 4,828, Visits: 11,179
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




Help us to help you. For better, quicker and more-focused answers to your questions, consider following the advice in this link.

When you ask a question (and please do ask a question: "My T-SQL does not work" just doesn't cut it), please provide enough information for us to understand its context.
Post #1517970
Posted Wednesday, November 27, 2013 3:31 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 3:27 PM
Points: 12,185, Visits: 9,134
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.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1517971
Posted Wednesday, November 27, 2013 9:30 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Yesterday @ 7:00 AM
Points: 85, Visits: 336
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.
Post #1518130
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse