Beginning Microsoft SQL Server 2008 ... - S3 Tech Training

Chapter 19: Playing Administrator
You can then fill out a schedule indicating what times this operator is to receive e-mail notifications for
certain kinds of errors that you’ll see on the Notifications tab.
Speaking of that Notifications tab, go ahead and click over to that tab. It should appear as in Figure 19-2.
Figure 19-2
Until you have more alerts in your system (we’ll get to those later in this chapter), this page may not
make a lot of sense. What it is about is setting up which notifications you want this operator to receive
depending on which defined alerts get triggered. Again, hard to understand this concept before we’ve
gotten to alerts, but suffice to say that alerts are triggered when certain things happen in your database,
and this page defines which alerts this particular operator receives.
Creating Jobs and Tasks
566
As I mentioned earlier, jobs are a collection of one or more tasks. A task is a logical unit of work, such as backing
up one database or running a T-SQL script to meet a specific need such as rebuilding all your indexes.
Even though a job can contain several tasks, this is no guarantee that every task in a job will run. They will
either run or not run depending on the success or failure of other tasks in the job and what you’ve defined
to be the response for each case of success or failure. For example, you might cancel the remainder of the
job if one of the tasks fails.
Just like operators, jobs can be created in Management Studio as well as through programmatic constructs.
For purposes of this book, we’ll stick to the Management Studio method. (Even among highly
advanced SQL Server developers, programmatic construction of jobs and tasks is very rare indeed.)