Please show how to check if a Job already Exists ?

Also, if a Job is set to run, say weekly, and during the week the server is shutdown and later restarted missing the Job interval period, does EDB know it may have missed a job interval during that shutdown period and it compensates accordingly - say by running the Job on startup ?

Andrew

>Please show how to check if a Job already Exists ?

SELECT * FROM Configuration.Jobs

>Also, if a Job is set to run, say weekly, and during the week the server is shutdown and later restarted missing the Job interval period, does EDB know it may have missed a job interval during that shutdown period and it compensates accordingly - say by running the Job on startup ?

No idea

Thanks Roy, I kind of new how to check but wanted to be sure, I particularly wanted to know about missed interval backups

>> does EDB know it may have missed a job interval during that shutdown period
>> and it compensates accordingly - say by running the Job on startup ?

The JOBs configuration table includes a "LastRun" TIMESTAMP field, and various fields controlling the interval of operation.

If a running instance of EDBSRVR finds any job which is due to be run on the basis of these fields, it tries to run this job.

If the server (either the whole computer or the EDBSRVR) has been "off" for multiple intervals it will still only be run once.

Note there is also a "number of times to retry a job" setting in the SERVER settings. This means if running the JOB generates an error it will not retry endlessly. I attach an image showing where this is set up.

As a secondary note Andrew,

Remember you have the LogEvents table:

SELECT *
FROM Configuration.LogEvents
WHERE Function = 'Execute Job'

Will give you useful data to help analyse JOB activity.