August 9, 2018 at 11:33 am
There is another data flow there already., and a couple of other tasks.
is it OK to add another data flow to the package without precedence constraints as shown on the attached image?
The 'Parents Data' data flow has nothing to do with any other dataflows/tasks, and the new data flow can probably be added WITH a precedence constraint before or after any existing tasks.
Is it a bad practice not to connect data flow to other control flow items?
Or since it has been added the last it is assumed that the new data flow will be executed after other tasks have been completed?
Thank you!
Likes to play Chess
August 9, 2018 at 11:48 am
VoldemarG - Thursday, August 9, 2018 11:33 AMThere is another data flow there already., and a couple of other tasks.
is it OK to add another data flow to the package without precedence constraints as shown on the attached image?
The 'Parents Data' data flow has nothing to do with any other dataflows/tasks, and the new data flow can probably be added WITH a precedence constraint before or after any existing tasks.
Is it a bad practice not to connect data flow to other control flow items?
Or since it has been added the last it is assumed that the new data flow will be executed after other tasks have been completed?Thank you!
Adding a dataflow without precedence constraints merely means that it will execute in parallel with other tasks which are not bound by precedence constraints.
If such parallelism works in your case, go ahead and do it – you may find that this provides a speed boost. But watch out for conflicts when using parallelism (eg, parallel tasks accessing the same file or table).
If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply