SQL Server Agent jobs and dependencies

I have 6 SQL Server Agent jobs that have to run every hour.  5 of them are jobs which update data from a Progress database using ODBC to a SQL Server stored on a network computer.  The 6th job updates the "updated" tables from the network computer to the SQL Server on the webserver.   The 5 jobs are timed to finish running by 4 after the hour.  The 6th and final job has to run by 6 after the hour.  Most of the time this runs fine.  But during the 1st - 5th of the month (Heavy traffic time) some jobs may fail.  Is there a way for the 6th job to NOT run if any of the previous 5 jobs have failed?
BSitkoAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
SNilssonConnect With a Mentor Commented:

In your fifth job you can add the sixth job as a step to be run if the fifth was ok.

You can also do this in a DTS package and add decision ways depending on succes failure and in the order you want, so maybe you should check if using a dts package is something for you.

Post again if you have any questions about converting your current job's to dts.
0
 
arbertCommented:
Schedule them all under the same SQLAgent job....When you add a new step to the job, you can set dependencies based on the successful (or not successful) execution of the previous job/step.
0
 
BSitkoAuthor Commented:
Could I still schedule each of the individual "jobs" to run at different times?  i.e. Job1 = 11:59 , Job2 = 12:00 , Job3 = 12:00:30 ...etc.  Running them all back-to-back would take too long.  (About 10 minutes)
0
Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

 
arbertCommented:
Not in the scenario I gave above....You could possibly build an "indicator" table that you have the job write a flag to saying it's done...Then, in the jobs with dependencies, have them check this table before they run.....
0
 
BSitkoAuthor Commented:
Nothing programmatically can be done to tie in what's existing?  I somehow knew it wasn't going to be easy...
0
 
SoftEng007Connect With a Mentor Commented:
run this query to check if a job failed:

exec [sp_help_jobhistory] @job_name='Name goes here',@Step_id =0 ,@run_status=0 --,@start_run_date='date here' --to filter to a single days run

a 0 run status for step 0 (job outcome) indicates the job failed.

you can use this in an if exists query and raise an error in it returns this will fail you 6 job and then it won't run.
0
 
arbertCommented:
SoftEng007, very good idea......
0
 
SoftEng007Commented:
Thanks,
I had to use this method to implement email notifications to user groups when certain batchjobs failed.
They had a very convoluted process in place to sync user jobs together.
0
 
SNilssonCommented:

That is if job five have finished, if it's still running jobhistory wont have any 'success' data in it.
0
 
arbertCommented:
"They had a very convoluted process in place to sync user jobs together."

Ingenuity by necessity :)
0
 
SoftEng007Commented:
SNilsson,
you are quite correct.
i tried to answer
>>Is there a way for the 6th job to NOT run if any of the previous 5 jobs have failed?

There are other methods and sysobjects tables that can be queried if you need to know if a job has started AND finished.

you could for instance change the step_id to look for 1 which is the first step. if it's not there the job hasn't started.
OR
you could use a while loop and an not exist check against step_id=0
when you find it then run my query listed in my previous post to determine the outcome.
0
 
BSitkoAuthor Commented:
Give me some time over the weekend to check these ideas and I'll get back to you.  (Sorry for the delayed response but I've been out of the office).  500 points will be worth the wait?  right?  
0
 
BSitkoAuthor Commented:
SoftEng007 ... where would such code go?  Would it preceded job 6 running?  Where?  Forgive this type of question but I'm just not sure.
0
 
SoftEng007Commented:
job 6 should have 2 steps.
The first step is the check step it should use the (if exists...) to check the job history.

use raise error if the row is not there.  for the job set this step to fail on error. goto next step on sucess.

step 2 should run your process.
0
All Courses

From novice to tech pro — start learning today.