May 23, 2013 at 7:34 am
We do have the need of running several jobs daily... jobs that update custom tables, create reports etc.
What is the best practice? To have several jobs (one for each SP) or to group SP's into job step and have fewer jobs that are going to run for longer time since they have several steps?
May 23, 2013 at 10:32 am
It really depends on what you are trying to do and how you want to manage it.
Here are some things to consider:
Are these tasks dependent on each other?
Can any of these tasks be run in parallel?
Do you want to run all these tasks at the same time each day?
Would you at any point want to temporarily disable some tasks but not the others?
Do you want notifications if a task fails?
May 23, 2013 at 10:34 am
Multiple jobs will give you greater flexibility if you need to rerun a job or change the schedule. If the procedures are closely functionally related I would create a job with multiple steps.
If SP1 always needs to run before SP2 the one job with multiple steps makes sense. If SP1 has nothing to do with SP2 then break them out.
May 23, 2013 at 12:14 pm
Are these tasks dependent on each other? No.
Can any of these tasks be run in parallel? Yes.
Do you want to run all these tasks at the same time each day? Most of them will run "about the same time"
Would you at any point want to temporarily disable some tasks but not the others? Yes.
Do you want notifications if a task fails? Yes.
I'm just wondering what is the best practice regarding performance and management.
May 23, 2013 at 12:28 pm
With your answers, I think you answered your own question.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply