I need to test SQL Agent over a period of time, so need to change the system clock into the future quite often (and back)... don't worry it's only my local machine not a server :-)
The trouble is when I set it back again to the present date time, the next run date still ad-hears to the future times.
e.g. If I've put my clock into the future and the job is set to run every minute and it was last run in 11/01/2080 01:01:00 then it's next run is 11/01/2080 01:02:00, even if I set the clock back to the present.
It is understandable that this is the normal behaviour of SQL Server. Is there a way of resetting the next run date easily?
I've tried running the job manually but it has no effect on the next run time.