Last post Dec 15, 2016 04:20 PM by bbcompent1
Dec 15, 2016 03:38 PM|devrathnd|LINK
Dec 15, 2016 04:20 PM|bbcompent1|LINK
Ok, is your task schedule database driven? As in the database contains details on when the service should run? In my instance, I have the start time, end time, and day managed by the database along with the read time interval between attempts in minutes.
To accomplish this on a non-clustered environment running multiple servers, you would start each server's service at 15 second apart intervals. Then during the read time, you would have a field in there that would be next run date and time. You update the
run-date/time to the next time period. This way, each server will query the DB asking when the next time to run is. Does that make sense? How are you doing it now?