Asynchronous still hangs scheduler when job hangs

We are using 24x7 to run about a dozen reports. A few are SQL queries, but most are batch files, spreadsheets and access db's triggered to autorun reports through VBA.

Each report may have up to five jobs chained together (e.g, run sql query, then format through spreadsheet, then email report). If one of the jobs fails, then we don't want the chained jobs to run. This does work well.

However, if the job scheduled for 2AM fails, then we still need the job scheduled for 2:30 AM to run. This is not working. We have set all jobs to run asynchronously, but still, when the 2AM job hangs, the 2:30 AM job is never called. And even though "asynchronous" is selected, the scheduler is hung and the gui can't be used until the hung job is killed.

Further, when we come in the morning, and kill the hung job, then all the other jobs try to run at once, causing havoc with our databases.

We need a way to allow a job to hang (or to take longer than usual) without hanging the scheduler and causing all of the other scheduled jobs to fail.

	Quote:
	We have set all jobs to run asynchronously

	Quote:
	kill the hung job, then all the other jobs try to run at once

You've got a problem here. Do not use Async mode for anything other than jobs that run forever. I mean jobs that run for many hours or run a never ending loop.

Use multiple job queues to parallelize job streams. Also make sure all your reporting jobs are set to run in Detached mode. In that case each stream will be totally independent and it wouldn't matter when jobs in other queues fail or get killed as they aren't going to affect other queues.

Hope this helps.