![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have a number of OLAP cubes to be processed. There are a series of steps to process shared dimensions, then the cube-processing tasks. All the cube-processing tasks have workflow from last shared-dim task to execute "On Success", but there are no workflows set up among the cube tasks. They are all siblings waiting on the last shared-dim task. Will these full-process tasks execute consecutively? Or might separate threads be launched to execute multiple cube tasks concurrently? LMcPhee |
#3
| |||
| |||
|
|
They should be free to execute when they want. The package will try to fire them on startup if they are not constrained. If you want to execute them in order then you need to use Workflow Constraints ideally. -- Allan Mitchell www.SQLDTS.com www.SQLIS.com www.Konesans.com "lmcphee" <lmcphee (AT) discussions (DOT) microsoft.com> wrote in message news:08150926-2412-430D-AE5B-EFDB4C35EDD4 (AT) microsoft (DOT) com... I have a number of OLAP cubes to be processed. There are a series of steps to process shared dimensions, then the cube-processing tasks. All the cube-processing tasks have workflow from last shared-dim task to execute "On Success", but there are no workflows set up among the cube tasks. They are all siblings waiting on the last shared-dim task. Will these full-process tasks execute consecutively? Or might separate threads be launched to execute multiple cube tasks concurrently? LMcPhee |
![]() |
| Thread Tools | |
| Display Modes | |
| |