???
Reporting Services for SQL Server 2000 introduced the idea of a shared schedule.
However, in SQL Server 2000, you actually implemented a shared schedule via the application
rather than through the SQL Agent itself. SQL Agent 2005 now has built-in support
for shared schedules.
The shared schedule concept has both positives and negatives. It simplifies scheduling
and reduces the likelihood of human error, but if overused, backup jobs can queue up
behind each other, or you could overload the server capacity by running everything at
once. Be sure to assess the impact of any shared schedules.
Jobs and Job Steps
When you define a schedule, you must have a job to execute. Many novice DBAs mistakenly
assume that only one action may be executed. Actually, a number of job steps can be
executed, each with a precedence defined to control the overall order in which the steps
execute. Figure 5-1 illustrates a job step in which the success action is to continue on to
the next step in the overall job.
CHAPTER 5 n CREATING A BACKUP/RECOVERY PLAN 114
Figure 5-1. In the Advanced section, you have control over what happens when a job step
is successful and over what happens when it fails.
Pages:
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243