January 3, 2014 at 10:09 am
if it shows that it will run 2/1 then the schedule is enabled.
I'll revert back to, 'delete the schedule and make it again'
.
January 3, 2014 at 1:22 pm
Bill (DBAOnTheGo) (1/3/2014)
if it shows that it will run 2/1 then the schedule is enabled.I'll revert back to, 'delete the schedule and make it again'
OK, Bill, I've taken your advice. I removed the schedule from the job and then created a new one, with a different name (I don't know if the old schedule is still out there or not). As it turns out that SQL job was the only one that used that schedule, so I don't harm anything else. Then I double checked it in Activity Monitor, and it now shows it as going to run on April 1st, which is what I want it to do.
Just out of curiosity, suppose I or someone else, were to run that SQL job manually before then? Will it still run on 4/1/2014 @ 12:05 AM? Or would it be rescheduled?
Kindest Regards, Rod Connect with me on LinkedIn.
January 5, 2014 at 10:45 pm
That is a good question. You have two easy options there.
1) Create a job that does something, anything. Maybe even select name from sys.databases
Set it to run based on that schedule. check that it's going to run april 1st. Now run it manually and then see if that changes
2) Run the job anyways and if the date changes, reset the schedule again.
Either of those should answer the question. My personal guess is that it will hold the correct schedule still, but I don't have my lab near me right now.
.
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply