March 11, 2009 at 6:40 am
When you are running a job manually, gthen you are given the option to start the job at a specific step.
Does SQL server agent 2005 have the ability to schedule the job, and still specify what step it starts at, or will it always just start at the first step in the sequence?
I have a lot of steps that are running the same package but setting some of the variables inside the package differently - depending on how I set up the schedule, I wanted a different step to run. The alternative for me would be to make a lot of singular jobs, with each one on its own schedule, but it just feels like there should be a way to do this, as there is a way to do it when you are running the package manually.
Thanks!
March 11, 2009 at 10:19 am
When you open a job in SSMS and go to the "Steps" tab, you can specify the start step but I don't think there's a way to connect that to a particular schedule.
Greg
March 11, 2009 at 10:36 am
You could possibly pass in global variables from the various schedules. But that would mean separate jobs for each schedule
March 12, 2009 at 8:55 am
Steve Jones - Editor (3/11/2009)
You could possibly pass in global variables from the various schedules. But that would mean separate jobs for each schedule
That was the only solution I could see to the problem too, I was just hoping I was being dense and there was a better solution 🙂
Thanks for the replies
March 19, 2009 at 11:23 am
It's been brought to my attention recently that there are several tables containing information about jobs and their schedules. does anyone know if it is possible to list through SQL the currently running job and the schedule that activated it?
If that was possible, then I could potentially just store these values for the job and schedule and set the variable in my package based on this information, which is what I essentially need...
Viewing 5 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply