ratinakage
Programmer
Hey guys,
I know you can disable a SQL job. What I want to know is, if anyone can think of a clever way to disable a job step?
Basically, I want to create a big SQL job with all the steps disabled. Then as the users of my app turn certain things on, the job steps should become activated (or enabled).
My first thought was to do something like this.
1. dummy step. Next step = 3
2. real step a Next step = 3
3. dummy step Next step = 5
4. real step b Next step = 5
5. dummy step Next step = 7
6. real step c Next step = 7
....
Where you basically have a job so that none of the steps are enabled and they are all skipped over. Then as things need to be enabled, you just change the next step to next step - 1 (or something like that)
Its a bit messy. Can you think of anything else?
Thanks,
I know you can disable a SQL job. What I want to know is, if anyone can think of a clever way to disable a job step?
Basically, I want to create a big SQL job with all the steps disabled. Then as the users of my app turn certain things on, the job steps should become activated (or enabled).
My first thought was to do something like this.
1. dummy step. Next step = 3
2. real step a Next step = 3
3. dummy step Next step = 5
4. real step b Next step = 5
5. dummy step Next step = 7
6. real step c Next step = 7
....
Where you basically have a job so that none of the steps are enabled and they are all skipped over. Then as things need to be enabled, you just change the next step to next step - 1 (or something like that)
Its a bit messy. Can you think of anything else?
Thanks,