I've used this method many times. Simply add another step to the first job, with the command type of T/SQL command and put something to this effect in the command box. <pre>exec sp_start_job @job_name='The Second Job' GO</pre> If the second job will run every time that the first job runs, then why not take the job steps from the second job and add them to the first job. This was it's a single seamless job. If you need the second job to be able to be run seperatly from the first then keeping them as two jobs will be the best bet. wow rotten answer, the jobs return a 1 or 0 you just need to capture the return code, then place that in an if statement.

I've used this method many times. Simply add another step to the first job, with the command type of T/SQL command and put something to this effect in the command box. <pre>exec sp_start_job @job_name='The Second Job' GO</pre> If the second job will run every time that the first job runs, then why not take the job steps from the second job and add them to the first job. This was it's a single seamless job. If you need the second job to be able to be run seperatly from the first then keeping them as two jobs will be the best bet. wow rotten answer, the jobs return a 1 or 0 you just need to capture the return code, then place that in an if statement.