Hey all,
I ran into a very wierd issue and looking for some input on this one. Here is the background
I have a thousand servers that are remote and they all basically run the same SQL job locally in the SQL Agent. Now for an update i had to alter the job schedule to change job timings for a one-time run, and then allow the job to run as normal. Now I know there aer many ways to do this but here is what I did (all through TSQL on the backside):
1) Created a new One-Time Job Schedule for the event timing I needed
2) Associated that schedule to the Jobs - thus creating 2 job schedules for the job
3) Disabled the other Job Schedule to allow the new schedule to run
I pulled a TSQL job schedule and everything slooked to be correct, however when it came time for the jobs to execute - they didn't (go figure). Investigating further I logged onto many of the instances and found that if I viewed the Jobs in the Job Activity Monitor, the jobs all showed the wrong scheduled time but if I edited the Job it did show the correct schedule with the other schedule disabled.
Really looking for some thoughts on this one