dbTalk Databases Forums  

Order of execution of tasks

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss Order of execution of tasks in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
lmcphee
 
Posts: n/a

Default Order of execution of tasks - 04-24-2006 , 11:13 PM






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

Reply With Quote
  #2  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: Order of execution of tasks - 04-25-2006 , 06:12 AM






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

Quote:
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



Reply With Quote
  #3  
Old   
lmcphee
 
Posts: n/a

Default Re: Order of execution of tasks - 04-25-2006 , 10:21 AM



The only reason I am considering having the cube tasks execute synchronously
is that it might be more efficient/faster. Plus when I experimented with this
with three cube tasks (all use a few common shared dimensions) I
occasionally get processing errors. I am concerned that having multiple
concurrrent cube tasks running which access common tables/dimensions may be
dangerous practice. Should I just make all the cube tasks siblings in the
workflow and trust AS 2000 to handle it? This would make implementation much
cimpler. To set up all the constraints to make it all synchronous would be a
major headache I think. For each cube there would be 3 separate paths to the
next cube's tasks (do nothing, incremental process, full process) and I would
have to set it up so the 3 paths merge. Repeat for every cube...

LMcPhee

"Allan Mitchell" wrote:

Quote:
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




Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.