Hi. I'm leveraging the power of the web to help me gather up some best practices for the following situation. I have a job, with over a hundred reports, set to run concurrently. Running sequentially is out of the question as it would take too long. Each report runs for 40+ mins.
The problem is this, when this job kicks off all the reports (up to the max # of processes) kick off simultaneously, leaving no room for other reports our users may be running. I would rather it behave like this.. Take the # of processes allowed, and only allow a certain percentage of that to be used up by the job, so the other portion can be free for our users.
I was going to break up this job into multiple sub-jobs of 10 and set those to run sequentially, but if someone knows a better solution, please, i'm all ears. Many thanks!