Setting the recurrence interval.

The recurrance interval is very straightforward. You will note one major kludge displayed in the screen shot above. The vast majority of jobs you create will be run on every business day. For most companies this means Monday - Friday. In order to accomplish this, you need to actually create a weekly schedule. This is due to the fact the SQL Server Agent does not give you any functionality to define what your business week consists of and allow you to schedule a job for every business day.

Creating a notification

The notifications for a job are one other area where an opprotunity was missed to add much better functionality. You can only specify a single operator to receive a notification for a single outcome of a job for each notification mechanism. This means you can not e-mail one operator is the job succeeds and another one if the job fails.

Setting notifications for the job.

For jobs that are critical to your environment, a notification should always be e-mailed to an operator whether the job succeeds or fails. This is simply because e-mail is the most unintrusive mechanism. If any critical job fails, an operator should be immediately paged to attend to the problem and an entry placed in the NT event log. A net send notification might also be appropriate here, but you have to remember that the machine being notified must be running. There is an option to automatically delete a job. I would not recommend using this option, because you will lose access to the history for that job.

SQL Server Agent 1 2 3 4 5 6 7 8 9