Periodic Restarts

Can you tell me a little more about the "periodic restart" option?

Specifically, I would like to know if this is an "orderly restart", or if currently running jobs are just aborted.

The situation is that I have found that 24x7 is fairly stable under a busy job load if restarted once daily.

I have many "file watch" jobs that can kick in at any time based on a customer sending a file to us. In some cases, it would be detrimental to just "pull the rug out from under" these jobs if they happen to be running at the time of the restart.

Any jobs are running detached, they should not be affected and should continue running because they are separate system processes. Any script type and database type jobs running non-detached should go down with the scheduler as they are part of the same process.

As far as I understand you don't want to "pull the rug out from under" these jobs, so that automatic restart is not good for you are using non-detached jobs.

The solution in this case is to ensure that jobs have their detached property set.

By the way, if you are running 24x7 as a service, you could also use Windows service restarts. The impact on running jobs in this case is the same as described above. Yet the difference is that in this case you have more control over restart time and dependencies, basically you can schedule a batch file running NET STOP “24x7 Scheduler” and then NET START “24x7 Scheduler” commands and you can add your own checks to verify no jobs are running, if they are running, you can make the restart job wait for the other jobs to complete.

Thanks for the info.

I am running 24x7 as an app because I need the ability to start jobs from incoming email and this requires MAPI which doesn't work from a service.

I run most jobs detached, so it sounds like it will work to restart the app daily.