March 1, 2015 at 5:51 am
We have a job that runs daily that today exhibited some strange behavior. Usually the job runs at 7:00 a.m. Because a database it depends on doesn't finish restoring until after that, one of my coworkers rescheduled the job to run at 8:30 a.m. He changed the schedule to pick up starting tomorrow (3/2/2015), but for some reason, no matter how we refreshed the job activity monitor, the job kept showing that it was going to run today at 8:30.
Can someone shed some light on why SQL Server is behaving this way?
I have some thoughts, but I'd like to see what other people say before I voice them. Pictures are attached.
March 3, 2015 at 2:09 pm
It's the year. The schedule was set to start on 3/2/2012 and since it was back dated to start then, the next run on 3/1/2015 would start at 8:30.
March 3, 2015 at 2:25 pm
Brandie Tarvin (3/1/2015)
He changed the schedule to pick up starting tomorrow (3/2/2015)
Starting three years ago tomorrow, you mean? 🙂
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 4, 2015 at 4:29 am
GilaMonster (3/3/2015)
Brandie Tarvin (3/1/2015)
He changed the schedule to pick up starting tomorrow (3/2/2015)Starting three years ago tomorrow, you mean? 🙂
DOH. I didn't even see 2012. I looked at that thing 3 times and saw 2015 each time.
BLEARGH. Just goes to show that have of what we see depends on what we expect to see. Thanks.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply