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

Chapter 19: Playing Administrator
574
Finally, we can go back to the Notifications node of the main New Job dialog box, shown in Figure 19-13.
Figure 19-13
This window lets you bypass the older alerts model and define a response that is specific to this one job;
we’ll just stick with what we already have for now, but you could define specific additional notifications
in this dialog box.
The last node in the list is the Targets node. This one generally falls in both the administrator and advanced
realms, as it is based on the idea of one SQL Server scheduling jobs onto other SQL Servers. Be aware
that it’s there for special needs, but we will otherwise save that topic for an advanced-level text.
At this point, you are ready to say OK and exit the dialog box. You’ll need to wait a few minutes before
the task will fire, but you should start to see log entries appear every five minutes in the Windows event
log. You can look at this by navigating to Start ➪ Programs ➪ Administrative Tools ➪ Event Viewer.
You’ll need to switch the view to use the Application log rather than the default System log.
Don’t forget that, if you’re going to be running scheduled tasks like this one, you need to have the SQL
Server Agent running for them to be executed. You can check the status of the SQL Server Agent by
running the SQL Server Configuration Manager and selecting the SQL Server Agent service, or by navigating
to the SQL Server Agent node of the Object Explorer in Management Studio.
Also, don’t forget to disable this job. (Right-click the job in Management Studio after you’ve seen that
it’s working the way you expect. Otherwise, it will just continue to sit there and create entries in your
Application log; eventually, the Application log will fill up and you can have problems with your system!)