LESSON: 2B MANAGING SQL SERVER 2000 AGENT JOB Objectives Managing SQL Server 2000 Agent Jobs Objectives In this section, you will learn about: • • • • ©NIIT 2B.1 Creating and managing SQL Server 2000 Agent alerts Creating operators Creating and managing SQL Server 2000 Agent jobs Troubleshooting SQL Server 2000 Agent jobs Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 1 of 31 Administering and Troubleshooting SQL Server 2000 In this lesson, you will learn about: Creating and Managing SQL Server 2000 Agent alerts Creating operators Creating and Managing SQL Server 2000 Agent jobs Troubleshooting SQL Server 2000 Agent jobs Administering and Troubleshooting SQL Server 2000 2B.2 Managing SQL Server 2000 Agent Jobs Pre-Assessment Questions ©NIIT 2B.3 1. Which of the following backup methods will you use to save the latest changes made to a filegroup? a) Differential Backup b) Filegroup Backup c) Differential Filegroup Backup d) Transaction Log Backup 2. Which of the following variables refers to the type of backup device that you want to use? a) Database_name b) Database_backup_filename c) Transactionlog_backup_filename d) Device_type Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 2 of 31 Administering and Troubleshooting SQL Server 2000 Managing SQL Server 2000 Agent Jobs Pre-Assessment Questions ©NIIT 3. Which of Manager a) b) c) d) the following keywords does the SQL Server 2000 Enterprise use to identify a corrupted database? SUSPECT VERIFYONLY WITH DIFFERENTIAL FILEGROUP 4. Which of a) b) c) d) the following reasons refers to unpredictable situations? Hardware Failures Natural Disasters Intentional Data Loss Accidental Data Loss Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 3 of 31 Administering and Troubleshooting SQL Server 2000 2B.4 Managing SQL Server 2000 Agent Jobs Pre-Assessment Questions 5. ©NIIT 2B.5 Which of the following backup methods of SQL Server is used to speed up the backup operation? a) Full Backup b) Filegroup Backup c) Transaction Log Backup d) Parallel Striped Backup Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 4 of 31 Administering and Troubleshooting SQL Server 2000 Managing SQL Server 2000 Agent Jobs Solutions to Pre-assessment Questions: Ans 1. c. Differential Filegroup Backup Ans 2. d. Device_type Ans 3. a. SUSPECT Ans 4. b. Natural Disasters Ans 5. d. Parallel Striped Backup ©NIIT Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 5 of 31 Administering and Troubleshooting SQL Server 2000 2B.6 INSTRUCTOR NOTES Start the session by telling the students that about SQL Server Agent services. Tell the students that SQL Server Agent service uses the following three components: Jobs Alerts Operators Tell the students about each component in detail. Also discuss about the following messaging methods used to send messages to the operators: E-mail Pager Net Send Explain these messaging methods in detail. You can also tell the students that a new operator can be defined using the sp_add_operator system stored procedure. Ensure that the following datafiles are installed on the student nodes: Customers.mdb Sales.mdb 2B.7 Administering and Troubleshooting SQL Server 2000 INTRODUCING SQL SERVER AGENT SERVICE Managing SQL Server 2000 Agent Jobs Introduction to SQLServerAgent Service • • SQL Server 2000 provides SQLServerAgent service to administer programmatically certain administrative tasks or server events that occur regularly. This service uses three components to accomplish the automation task. They are: • • • ©NIIT Alerts Operators Jobs Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 6 of 31 Administering and Troubleshooting SQL Server 2000 2B.8 Managing SQL Server 2000 Agent Jobs Introduction to SQLServerAgent Service (Contd.) • Alerts: • • • • ©NIIT 2B.9 An alert is an event or error message that occurs in SQL Server and sent to the users via e-mail, pager, or Net Send. The error message is written to the Windows NT Application log file. You can define the conditions in which an alert occurs. Alerts can takes action to notify one or more operators. It can also forward the event from one server to another and can execute a job. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 7 of 31 Administering and Troubleshooting SQL Server 2000 Managing SQL Server 2000 Agent Jobs Introduction to SQLServerAgent Service (Contd.) • Operators: • • ©NIIT An operator is a user who receives the messages when an alert is fired. Operators receives the notification from SQL Server Agent using one of three messaging methods: E-mail, Pager, Net Send. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 8 of 31 Administering and Troubleshooting SQL Server 2000 2B.10 Managing SQL Server 2000 Agent Jobs Introduction to SQLServerAgent Service (Contd.) • Jobs : • • • • ©NIIT A job is a series of steps that are performed sequentially by SQL Server Agent. Using jobs, you can define schedules for the execution of task. In addition, using jobs you can define the administrative task that can be monitored for success or failure each time it executes. The defined tasks can be executed on one local server or multiple remote servers. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 9 of 31 SQL Server 2000 provides the SQLServerAgent service to programmatically administer certain administrative tasks or server events that occur regularly. The SQLServerAgent service uses three components to accomplish this task. They are: Alerts Operators Jobs Alerts An alert is an event or error message that occurs in SQL Server and is sent to the users via e-mail, pager, or Net Send. The error message is written to the Windows NT Application log file. You can define the conditions in which an alert occurs. An alert can take action to notify one or more operators. It can also forward the event from one server to another and can execute a job. 2B.11 Administering and Troubleshooting SQL Server 2000 Operators An operator is a user, who receives the messages when an alert is fired. Operators receive the notification from SQL Server Agent using one of three messaging methods: E-mail: SQLServerAgent service sends notifications to operators using e-mail. This is possible only if SQLAgentMail has been previously configured. The SQLServerAgent service should be using the domain user account that must have a MAPI messaging profile on the computer on which SQLServerAgent is running. You can also use group e-mail to send notifications to multiple operators. However, you need to test the e-mail configuration before sending the notifications to the operators. Pager: SQLServerAgent service sends notifications to operators using a pager. This notification is implemented using e-mail and a third-party paging software. Since pager notifications require an e-mail, SQLAgentMail must be configured. In addition, you need to prepare a work schedule for each operator who needs to be notified by pager. If the job requiring notifications for an operator conflicts with the work schedule, then the notification fails. Net Send: This utility is provided by the Windows NT and 2000 operating systems and is used to send messages across the network. NET SEND utility requires the Windows Messenger service to be running on the receiving and the transmitting computers. You can define a new operator using SQL Server Enterprise Manager or by executing sp_add_operator system stored procedure. The definition of operator is stored in the msdb.sysopeartors system table. Jobs A job is a series of steps that are performed sequentially by SQLServerAgent. Using jobs, you can define schedules for the execution of task. In addition, using jobs you can define the administrative task that can be monitored for success or failure each time it executes. The defined tasks can be executed on one local server or multiple remote servers. Administering and Troubleshooting SQL Server 2000 2B.12 INSTRUCTOR NOTES Next, you need to discuss about SQL Server 2000 alerts in detail. Also tell the students about the attributes of SQL Server alerts and messages. Now, tell the students about creating alerts using the Create Alert wizard of SQL Server 2000 Enterprise Manager. To explain the process of creating alerts, present the students with a business problem that requires creating alerts using the Create Alert wizard. Discuss the solution of the problem in detail. You can divide the solution in to logically related tasks for better understanding of the process. Now, you can ask the students to perform the process of creating alerts using the SQL Server 2000 Enterprise Manager as a practice exercise. Finally, discuss the steps to review the details of the existing alerts and alert history using SQL Server 2000 Enterprise Manager. You can end the session by telling the students about troubleshooting SQL Server agents, jobs, and alerts. 2B.13 Administering and Troubleshooting SQL Server 2000 CREATING AND MANAGING SQL SERVER 2000 AGENT ALERTS You can use the components of SQL Server 2000 Agent services such as alerts to provide notification for various events. You can create alerts using the Create Alert Wizard of the SQL Server 2000 Enterprise Manager. Introducing Alerts Managing SQL Server 2000 Agent Jobs Introducing Alert • • • • • ©NIIT You can specify an alert to provide notification on event and performance condition. You can also define alerts to execute jobs in response to specific events or performance condition. SQL Server Agent monitors the Windows application log and compares each SQL Server Agent logged with the previously defined alerts. If a match is found during the comparison process, an event alert is fired. The different types of system alerts are stored in the sysmessages table of the master system database of SQL Server 2000. You can define your own alerts using SQL Server 2000 Enterprise Manager and store them in the sysmessages table. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 10 of 31 Administering and Troubleshooting SQL Server 2000 2B.14 Managing SQL Server 2000 Agent Jobs Introducing Alert (Contd.) • ©NIIT The following are the main attributes of the SQL Server alerts and their messages: • Error number • Message string • Severity • State code • Procedure name • Line number Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 11 of 31 You can specify an alert to provide notification for events such as user-defined errors and for describing the performance condition. You can also define alerts to execute jobs in response to specific events or performance condition. All these events are written to Windows application log after which the Windows application log notifies the SQL Server Agent about the occurrence of the logged events. SQL Server Agent monitors the Windows application log and compares each SQL Server Agent logged with the previously defined alerts in the msdb.sysalerts system table. If a match is found during the comparison process, an event alert is fired. The SQL Server Agent processes these alert and checks the msdb.sysnotifications system table to send notification, such as e-mail, pager, or net send. In addition, SQL Server Agent checks the msdb.sysoperators system table to identify the operator for sending notification. SQL Server Agent also monitors SQL Server performance objects and counters. If the value of the performance object and their associated counters is lower than, equal to, or more than the specified value of the object and their counters, the SQL Server Agent issues a performance condition alert. The performance condition alert can also be created for SQL Server 2000 resources that include databases, locks, buffer manager, cache manager, SQL Statistics, and access methods. These different types of system alerts are stored in the sysmessages table of the master system database of SQL Server 2000.You can define your own alerts using SQL Server 2000 Enterprise Manager and store them in the sysmessages table. Each system alert has certain attributes that distinguish it from the user-defined alerts. The following are the main attributes of the SQL Server alerts and their messages: 2B.15 Administering and Troubleshooting SQL Server 2000 Error number: Each error has a unique number. Message string: It contains information about the cause of the error, place where the error has occurred, and the object concerned with this error. Severity: It is a numeric value. Low numeric value of severity indicates information messages whereas high numeric values indicate serious errors. State code: It is used to find the source code location of the error and is used by Microsoft support engineers. Procedure name: It contains the name of the stored procedure if the error has occurred in a stored procedure. Line number: It indicates the line number of the Transact-SQL statement in the stored procedure, which has caused the error. You need to be a member of the sysadmin server role, to define alerts. Administering and Troubleshooting SQL Server 2000 2B.16 CREATING ALERTS Managing SQL Server 2000 Agent Jobs Creating Alerts Using Create Alert Wizard • ©NIIT The System Administrator, James of Mac Aluminum, Inc. wants to generate an alert for the backup operations of Customers database. James wants to fire an alert when an insufficient resource occurs during backup operation. Finally, James wants to assign the name of the generated alert as ‘Backup Alert’. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 12 of 31 Problem Statement The System Administrator, James of Mac Aluminum, Inc. wants to generate an alert for the backup operations of all databases. James wants to fire an alert when an insufficient resource occurs during backup operation. Finally, James wants to assign the name of the generated alert as ‘Database Backup’. 2B.17 Administering and Troubleshooting SQL Server 2000 Solution Managing SQL Server 2000 Agent Jobs Task List • • • • ©NIIT Open the New Alert Properties dialog box. Define the severity level. Specify the database in which error must occur. Verify that the alert has been created. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 13 of 31 To solve the preceding problem, perform the following tasks: 1. Open the New Alert Properties dialog box. 2. Define the severity level. 3. Specify the database in which error must occur. 4. Verify that the alert has been created. Administering and Troubleshooting SQL Server 2000 2B.18 1: Open the New Alert Properties dialog box Action: 1. Click StartÆAll ProgramsÆMicrosoft SQL ServerÆEnterprise Manager, to open the Enterprise Manager console of SQL Server 2000. 2. Expand Console RootÆMicrosoft SQL ServersÆSQL Server Group. Select the default instance. 3. Expand the default instance. Select and expand the Management option, to reach the SQL Server Agent. 4. Expand SQL Server Agent. Right-click Alerts and select New Alert from the pop-up menu to open the New Alert Properties dialog box. Ensure that the SQL Server Agent Service is running. 5. In the Name text box, enter Backup Database, as shown. 2B.19 Administering and Troubleshooting SQL Server 2000 2: Define the severity level Action: 1. Under Event alert definition section, select 017-Insufficient Resources option from the Severity drop-down list, as shown. 3: Specify the database in which error must occur Since James wants to fire an alert for all the databases, hence all the databases need to be selected from the Database name drop-down list. Action: 1. Verify that All Databases is selected in the Database name drop-down list. 2. Click OK to close the New Alert Properties dialog box. Administering and Troubleshooting SQL Server 2000 2B.20 4: Verify that the alert has been created Result: You can view the details of all the existing alerts using the SQL Server 2000 Enterprise Manager. It is essential that you must be a member of the sysadmin server role to view the details of the existing alerts. The following are the steps to view the details, properties, and history of the existing alerts using SQL Server 2000 Enterprise Manager: 1. From SQL Server 2000 Enterprise Manager, expand the Microsoft SQL ServerÆ SQL Server GroupÆ SQL Server default instanceÆ Management option. 2. From the Management option, expand the SQL Server Agent option. 3. Select the Alerts option. The details pane displays all the existing alerts. 4. In the details pane, click the Name column to sort the displayed alerts. 5. The Enabled column displays the status of the displayed alerts. 6. The details of the alerts, such as Severity, Error, Last Occurred, Email, Pager, Net Send, and Count are also displayed, as shown. 2B.21 Administering and Troubleshooting SQL Server 2000 To view the properties of an alert, right-click the specified alert and select the Properties option. You can also create an alert using the Create Alert Wizard. To invoke the Create Alert Wizard, you first need to select the Wizards command from the Tools menu. INSTRUCTOR NOTES Now, you can explain creating operators and fail-safe operators using SQL Server 2000 Enterprise Manager. To explain the process of creating operators and fail-safe operators, present the students with a business problem that requires creating an operator and a fail-safe operator. Discuss the solution of the problem. To help the students to effectively understand the process, divide the solution in to logically related tasks and then explain each task in detail. Additional Inputs Using Transact-SQL to Create Operators You can create operators using the sp_add_operator system stored procedure of Transact-SQL. The following is the syntax of the sp_add_operator system stored procedure: sp_add_operator [@name = ] ‘name’ [, [@email_address = ] ‘email_address’ [, [@pager_address = ] ‘pager_address’ In the above syntax: The @name keyword takes the value specified with the name variable. The name variable refers to the name of the operator to be created. The @email_address keyword takes the value specified with the email_address variable. The email_address variable refers to the e-mail address of the newly created operator. The @pager_address keyword takes the value specified with the pager_address variable. Administering and Troubleshooting SQL Server 2000 2B.22 The pager_address variable refers to the pager address of the newly created operator You can use the sp_update_operator system stored procedure to update the existing operators. 2B.23 Administering and Troubleshooting SQL Server 2000 CREATING OPERATORS Managing SQL Server 2000 Agent Jobs Creating Operators • ©NIIT The System Administrator of Mac Aluminum, Inc. wants to monitor backup operations and their results for all the databases. The System Administrator wants to assign this task to James and designate him as an SQL Server 2000 Operator. To designate James as an Operator, the System Administrator wants to configure the operator options in SQL Server 2000. The System Administrator wants the notification of result of backup operations should be done through e-mail, and NET SEND utility of Windows operating system. The e-mail, and NET SEND addresses of James are ‘james@macaluminium.com’ and ‘James’ respectively. In case of failure on notifying the message to the Operator, the System Administrator wants to notify the results of backup operations to another operator Scott who is designated as a failsafe operator by SQL Server 2000. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 14 of 31 Problem Statement The System Administrator of Mac Aluminum, Inc. wants to monitor backup operations and their results for all the databases. The System Administrator wants to assign this task to James and designate him as an SQL Server 2000 Operator. To designate James as an Operator, the System Administrator wants to configure the operator options in SQL Server 2000. The System Administrator wants the notification of result of backup operations should be done through e-mail, and NET SEND utility of Windows operating system. The e-mail, and NET SEND addresses of James are ‘james@macaluminium.com’ and ‘James’ respectively. In case of failure on notifying the message to the Operator, the System Administrator wants to notify the results of backup operations to another operator Scott who is designated as a fail-safe operator by SQL Server 2000. Administering and Troubleshooting SQL Server 2000 2B.24 Solution Managing SQL Server 2000 Agent Jobs Task List • • • • ©NIIT Configure Configure Configure Verify the operator details. notification details. fail-safe operator details. operator configuration. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 15 of 31 To solve the preceding problem, perform the following tasks: 1. Configure operator details. 2. Configure notification details. 3. Configure Fail-safe operator details. 4. Verify the operator configuration. 2B.25 Administering and Troubleshooting SQL Server 2000 1: Configure operator details You can define a new operator using SQL Server Enterprise Manager or by executing sp_add_operator system stored procedure. The definition of operator is stored in the msdb.sysoperators system table. Action: 1. Select StartÆAll ProgramsÆMicrosoft SQL ServerÆEnterprise Manager, to open the Enterprise Manager console. 2. In the Console Root, expand Microsoft SQL ServersÆSQL Server GroupÆDefault instanceÆManagementÆSQL Server Agent container. 3. Right-click the Operators container and then click the New Operator option, to open the New Operator Properties dialog box. 4. Type James in the Name text box. 5. Type James@macaluminium.com in the E-mail name text box. 6. Type James in the Net send address text box. Administering and Troubleshooting SQL Server 2000 2B.26 2: Configure notification details In the Notifications screen, you can select one or more alerts that will be notified to the operators. You can also specify new task by selecting Job option. Action: 1. Click the Notifications tab. 2B.27 Administering and Troubleshooting SQL Server 2000 2. Verify that the Alerts option is selected in the Notifications screen. Select Backup Database as the Alert Name and select E-mail, and Net Send as the notification media, as shown. 3. Click the OK button to close the New Operator Properties dialog box. 3: Configure Fail-safe operator details A fail-safe operator is an operator who receives the message, when SQL Server Agent services fails to deliver the message to the defined operator. 1. Right-click the SQL Server Agent and select the Properties option to open the SQL Server Agent Properties dialog box. Administering and Troubleshooting SQL Server 2000 2B.28 2. Click the Alert System tab. In the Fail-safe operator section, select New Fail-Safe Operator from the Operator drop-down list, as shown. 3. The New Operator Properties dialog box appears. In the Name text box, enter Scott. 4. In the E-mail name text box, enter Scott@macaluminium.com. In the Net send address text box, enter Scott, as shown. 5. Click OK to close the New Operator Properties dialog box. 2B.29 Administering and Troubleshooting SQL Server 2000 6. Verify that the Notify using option as E-mail is selected. In addition, select the Net send option, as shown. 7. Click the OK button to close the SQL Server Agent Properties dialog box. 4: Verify the operator configuration Action: Click the Operators in the console tree. Notice that James and Scott operators appear in details pane. Administering and Troubleshooting SQL Server 2000 2B.30 INSTRUCTOR NOTES Next, tell the students about jobs in SQL Server 2000. Tell the students that jobs are a set of steps performed sequentially by SQL Server Agent services. Explain job steps and tell the tell the students that the following job steps are supported by SQL Server 2000: Operating system commands or CMDExec commands Transact-SQL statements Microsoft ActiveX scripts Replication tasks Explain each type of job step in detail. Now, you can tell about the job step process and job scheduling in detail. Now you can tell the students about creating agent jobs using the Create Job wizard of SQL Server 2000. To help the students to understand the process of creating agent jobs, present the students with a business problem that requires creating agent jobs. Discuss the solution of the problem in detail. Now, you can ask the students to perform the process of creating agent job using the SQL Server 2000 Enterprise Manager as a practice exercise. Next, discuss about the multiserver jobs, its components, and the processing of multiserver jobs. Then, discuss the steps to review the details of the existing jobs and job history using the SQL Server 2000 Enterprise Manager. 2B.31 Administering and Troubleshooting SQL Server 2000 CREATING AND MANAGING SQL SERVER 2000 AGENT JOBS Managing SQL Server 2000 Agent Jobs Creating and Managing SQL Server 2000 Agent Jobs • • • ©NIIT Jobs can be defined as a set of tasks performed sequentially by SQL Server 2000 Agent services. The action performed by jobs on database or server is known as job steps. SQL Server 2000 supports job steps that can be: • Operating system commands or CMDExec commands • Transact-SQL statements • Microsoft ActiveX scripts • Replication tasks Job Step Process: • You can configure a job step to perform multiple jobs sequentially on success or failure of a job process. • A job process can also be configured to quit or report its success or failure. For example, you can program a job step to continue with the subsequent steps or quit the job and report its success or failure. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 16 of 31 Administering and Troubleshooting SQL Server 2000 2B.32 Managing SQL Server 2000 Agent Jobs Creating and Managing SQL Server 2000 Agent Jobs (Contd.) Export Database On Success On Failure Update Database Success Report Backup Database Failure Report ©NIIT 2B.33 Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 17 of 31 Administering and Troubleshooting SQL Server 2000 Managing SQL Server 2000 Agent Jobs Creating and Managing SQL Server 2000 Agent Jobs (Contd.) • Jobs Scheduling: • You can schedule a job to run continuously or at recurring intervals, such as hourly, daily, or weekly. • You can also schedule a job to run whenever SQL Server Agent starts or CPU utilization of a computer is idle. • Each job schedule can be enabled or disabled. ©NIIT Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 18 of 31 Jobs are a set of steps that are performed by the SQL Server Agent services, sequentially. You can schedule a job to run sequentially or at recurring intervals. You can create a job using the Create Job wizard. Working with Jobs Jobs can be defined as a set of tasks performed sequentially by SQL Server 2000 Agent services. The action performed by jobs on database or server is known as job steps. SQL Server 2000 supports job steps that can be: Operating system commands or CMDExec commands Transact-SQL statements Microsoft ActiveX scripts Replication tasks Administering and Troubleshooting SQL Server 2000 2B.34 Operating System Commands or CMDExec Commands The operating system commands contains the full path to all the executable files and command. This path helps SQL Server Agent to find the application source. The command ends with extension .bat, .cmd, .com, or .exe. All the operating system commands includes a process exit code, which indicates the success or failure of the command. A process exit code with value zero indicates that the command is executed successfully. A process with any other exit code value indicates the failure of the command. Transact-SQL Statements In the job steps, you can specify the database in which Transact-SQL statements, functions, stored procedure, or extended stored procedure to be executed. In a single job steps, you can also specify multiple batches of Transact-SQL statements with embedded GO commands. In the job step, you need to include all the required variables and parameters. In addition, you can send the result set of a job to an output file. Microsoft ActiveX Scripts ActiveX script command can also be included in a job step and can be executed using CMDExec command. You can also include an ActiveX script file to be executed as a command for job step. In addition, the scripting language of the job step needs to be identified. Replication Tasks In a job step, you can include the following components of replication tasks: x x x x x 2B.35 Distribution Agent Log Reader Agent Merge Agent Queue Reader Agent Snapshot Agent Administering and Troubleshooting SQL Server 2000 Job Step Process You can configure a job step to perform multiple jobs sequentially on success or failure of a job process. A job process can also be configured to quit or report its success or failure. For example, you can program a job step to continue with the subsequent steps or quit the job and report its success or failure. The following figure displays the flow chart of sequential configuration of job step: On Success On Failure Export Database Update Database Success Report Backup Database Failure Report In the above figure, on successful execution of export database task, the update database task occurs. After successful execution of update database task, the backup database task occurs. On successful backup of database job step, it displays the success report. On failure of each job step, it displays the failure report. To notify the success or failure of a job process, you must configure the operators. When a job failure occurs, Windows event viewer automatically logs it into Windows application log file that can be further viewed. Administering and Troubleshooting SQL Server 2000 2B.36 Jobs Scheduling You can schedule a job to run continuously or at recurring intervals, such as hourly, daily, or weekly. You can also schedule a job to run only for a single time or in response to a defined alert. You can also schedule a job to run whenever SQL Server Agent starts or CPU utilization of a computer is idle. Each job schedule can be enabled or disabled. You can run a job manually or in response to an alert whenever all schedules are disabled. To define each job schedule, you can execute the sp_add_jobschedule system stored procedure or can use SQL Server Enterprise Manager. All the job schedules are stored in the msdb.sysjobschedules system table. INSTRUCTOR NOTES Additional Inputs Using Transact-SQL to Create Jobs You can create jobs using the sp_add_job system stored procedure of Transact-SQL. The following is the syntax of the sp_add_job system stored procedure: sp_add_job [ @job_name = ] ‘job_name’ In the above syntax: The @job_name keyword takes the value specified with the job_name variable. The job_name variable refers to the name of the job you want to create. You can also create a new job using the sp_add_jobschedule, sp_add_jobstep, and sp_update_jobstep system stored procedures Configuring a Proxy Account You need to configure a proxy account if you want to create a job that contains CmdExec and ActiveX job steps and users who are not the members of the sysadmin server role own these job steps. The following are the steps to configure the proxy account: 2B.37 Administering and Troubleshooting SQL Server 2000 1. In the SQL Server 2000 Enterprise Manager, expand the Console Root option and then expand the Microsoft SQL Servers option. 2. Expand the SQL Server Group option and then expand the SQL Server default instance option. 3. Expand the Management option and right-click the SQL Server Agent option. This displays a pop-up menu. Select the Properties option from the pop-up menu. 4. This opens the SQL Server Agent Properties dialog box. Select the Job System tab. 5. In the Non-SysAdmin job step proxy account section, disable the selected option. 6. This displays the SQL Agent proxy account dialog box. Enter a user name in the User name text box, password in the Password text box, and the domain name in the Domain text box. 7. Click the OK button. This closes the SQL Agent proxy account dialog box. 8. Click the OK button. This closes the SQL Server Agent Properties dialog box and creates a proxy account. Administering and Troubleshooting SQL Server 2000 2B.38 CREATING SQL SERVER 2000 AGENT JOBS USING CREATE JOB WIZARD Managing SQL Server 2000 Agent Jobs Creating SQL Server 2000 AgentJobs Using Create Job Wizard • ©NIIT The System Administrator of Mac Aluminum, Inc. wants to take backup of Customers database. The System Administrator wants to perform this activity using Transact-SQL statement. In addition to this, the System Administrator wants the backup operation should be performed automatically on Friday of every week at 08:30 pm and this backup process will commence from 14th November 2004. Moreover, the System Administrator wants to notify the Operator James regarding the status of the backup operation. Finally, the System Administrator wants to name this backup operation as ‘Backup of Customer Database’. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 19 of 31 Problem Statement The System Administrator of Mac Aluminum, Inc. wants to take backup of Customers database. The System Administrator wants to perform this activity using Transact-SQL statement. In addition to this, the System Administrator wants the backup operation should be performed automatically on Friday of every week at 08:30 pm from 14th November 2002. Moreover, the System Administrator wants to notify the Operator James regarding the status of the backup operation. Finally, the System Administrator wants to name this backup operation as ‘Backup of Customer Database’. 2B.39 Administering and Troubleshooting SQL Server 2000 Solution Managing SQL Server 2000 Agent Jobs Task List • • • • • • ©NIIT Start the Create Job Wizard. Write the Transact-SQL Statements for backup operation. Set the backup schedule. Assign operator to notify status of backup operation. Assign name to backup operation. Verify the notification of job to an operator. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 20 of 31 To solve the preceding problem, perform the following tasks: 1. Start the Create Job Wizard. 2. Write the Transact-SQL Statements for backup operation. 3. Set the backup schedule. 4. Assign operator to notify status of backup operation. 5. Assign name to backup operation. 6. Verify the notification of job to an operator. Administering and Troubleshooting SQL Server 2000 2B.40 1: Start the Create Job Wizard. Action: 1. Click StartÆAll ProgramsÆMicrosoft SQL ServerÆEnterprise Manager, to open the Enterprise Manager console of SQL Server 2000. 2. Expand Console RootÆMicrosoft SQL ServersÆSQL Server Group. Select the default instance and click the Run a Wizard icon on the tool bar to open the Select Wizard dialog box. 3. Expand the Management container and select the Create Job Wizard option. Click the OK button to open the Create Job Wizard dialog box, as shown. 2B.41 Administering and Troubleshooting SQL Server 2000 4. The Welcome to the Create Job Wizard screen appears, as shown. Click the Next button to continue with the wizard. 2: Write the Transact-SQL statements for backup operations. Action: Administering and Troubleshooting SQL Server 2000 2B.42 1. Verify that Transact-SQL command option is selected from the Select job command type screen, as shown. Select the Operating-system shell command option to run batch scripts or applications. If you need to run scripts created using VBScript or JavaScript, select the Active script option. 2. Click the Next button to open the Enter Transact-SQL Statement screen. 3. In the Enter Transact-SQL Statement screen, select the Customers database from the Database name drop-down list. 2B.43 Administering and Troubleshooting SQL Server 2000 4. In the Transact-SQL statement text area, write the following Transact-SQL statement: 5. Click the Next button to continue with wizard. 3: Set the backup schedule Action: 1. In the Specify job schedule screen, select On a recurring basis option, as shown. Administering and Troubleshooting SQL Server 2000 2B.44 2. Click the Schedule button to open the Edit Recurring Job Schedule dialog box. 3. Verify that Weekly option is selected from the Occurs section. 4. Select Fri option from the Weekly section. Deselect Sun from the Weekly section. 5. Select Occurs once at from the Daily frequency section and set the time as 8:30:00 PM in the drop-down list. 6. Set Start date as 11/14/2004 in the Start date drop-down list of Duration section, as shown. 7. Click the OK button to close the Edit Recurring Job Schedule dialog box. 8. Click the Next button to continue with the Create a Job Wizard. 4: Assign operator to notify backup operation. Action: 2B.45 Administering and Troubleshooting SQL Server 2000 1. In the Job Notifications screen, select James from the E-mail drop-down list, as shown. 2. Click the Next button to continue with the wizard. 5: Assign name to backup operation. Action: 1. Enter Backup of Customer Database in the Job name text box of Completing the Create Job Wizard screen, as shown. Administering and Troubleshooting SQL Server 2000 2B.46 2. Click the Finish button to create the job. The job was created successfully message box appears, as shown. 3. Click the OK button to close the message box. 6: Verify the notification of job to an operator. Result: The notified operator receives an e-mail or Net Send notification after completion of job. In case of Net Send notification, a Messenger Services dialog box appears. For immediate notification, you can select the Now option in the Specify job Schedule screen. 2B.47 Administering and Troubleshooting SQL Server 2000 CREATING JOBS USING SQL SERVER ENTERPRISE MANAGER Managing SQL Server 2000 Agent Jobs Creating Jobs Using SQL Server 2000 Enterprise Manager • ©NIIT The System Administrator of Mac Aluminum, Inc. wants to take backup of Sales database. The System Administrator wants to perform this activity using Transact-SQL statement. In addition to this, the System Administrator wants the backup operation should be performed automatically on Wednesday of every week at 12:00 pm and this backup process will commence from 14th Nov 2004. Moreover, the System Administrator wants to notify the Operator Scott regarding the status of the backup operation. Finally, the System Administrator wants to name this backup operation as ‘Backup of Sales Database’. The System Administrator wants to perform this operation through SQL Server Enterprise Manager. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 21 of 31 Problem Statement The System Administrator of Mac Aluminum, Inc. wants to take backup of Sales database. The System Administrator wants to perform this activity using Transact-SQL statement. In addition to this, the System Administrator wants the backup operation should be performed automatically on Wednesday of every week at 12:00 pm and this backup process will commence from 14th Nov 2004. Moreover, the System Administrator wants to notify the operator Scott regarding the status of the backup operation. Finally, the System Administrator wants to name this backup operation as ‘Backup of Sales Database’. The System Administrator wants to perform this operation through SQL Server Enterprise Manager. Administering and Troubleshooting SQL Server 2000 2B.48 Solution To solve the preceding problem, perform the following tasks: 1. Open the new job properties dialog box. 2. Assign name to job. 3. Write the Transact-SQL Statements for backup operation. 4. Set the backup schedule. 5. Assign operator to notify the status of backup operation. 1: Open the new job properties dialog box. Action: 2: Assign name to job. Action: 3: Write the Transact-SQL Statements for backup operations. Action: 4: Set the backup schedule. Action: 5: Assign operators to notify the status of backup operations. Action: 2B.49 Administering and Troubleshooting SQL Server 2000 Multiserver Jobs Managing SQL Server 2000 Agent Jobs Multiserver Jobs • • • • • ©NIIT Multi server jobs are used to automate jobs on multiple servers in a network. To automate jobs on multiple servers, you need to define one master server and one or more target servers. The master server is responsible for distributing jobs to the target servers. The master server also receives the events from the target servers connected through a network. The master server defines and manages the schedules for all the jobs on the target servers. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 22 of 31 Multi server jobs are used to automate jobs on multiple servers in a network. To automate jobs on multiple servers, you need to define one master server and one or more target servers. The master server is responsible for distributing jobs to the target servers. The master server also receives the events from the target servers connected through a network. The master server defines and manages the schedules for all the jobs on the target servers. Administering and Troubleshooting SQL Server 2000 2B.50 Master Server Managing SQL Server 2000 Agent Jobs Master Server • • • • ©NIIT You can execute the sp_msx_enlist system stored procedures or can use SQL Server Enterprise Manager to define the master server. When you define a master server having a target server, SQL Server inserts a row in the systargetservers system table of the master server. SQL Server also creates a logon account for each target server with the suffix, _msx_probe. SQL Server also creates MSXOperator on the master server and on each target servers. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 23 of 31 As the master server requires a number of connections to target servers, you can define a master server on a computer having Windows 2000 or Windows NT operating system. You can execute the sp_msx_enlist system stored procedures or can use SQL Server Enterprise Manager to define the master server. When you define a master server having a target server, SQL Server inserts a row in the systargetservers system table of the master server. SQL Server also creates a logon account for each target server with the suffix, _msx_probe. In addition, SQL Server creates MSXOperator on the master server and on each target servers. 2B.51 Administering and Troubleshooting SQL Server 2000 Target Servers Managing SQL Server 2000 Agent Jobs Target Server • • • ©NIIT You can execute the sp_msx_enlist system stored procedures or can use the Make Target Server Wizard available in SQL Server Enterprise Manager to define target servers. SQL Server stores the definition of target server in the msdb.systargetservers system table. A target server can only be assigned to one master server. In addition, one target server cannot be a member of other master server. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 24 of 31 To define target servers, you can execute the sp_msx_enlist system stored procedures or can use the Make Target Server Wizard available in SQL Server Enterprise Manager. SQL Server stores the definition of target server in the msdb.systargetservers system table. When you define target server, it must belong to the Windows domain that the master server belongs to. A target server can only be assigned to one master server. In addition, one target server cannot be a member of other master server. Processing Multiserver Jobs After the creation of the master server and target servers, you can create jobs on the master server. The master server then executes these jobs on one or more target servers. The msdb.sysdownloadlist contains the jobs placed by the master server in a download list. The target server periodically connects to the master server to download any new or updated posted jobs. Administering and Troubleshooting SQL Server 2000 2B.52 REVIEWING SQL SERVER 2000 JOBS AND JOB HISTORY Managing SQL Server 2000 Agent Jobs Reviewing SQL Server 2000 Jobs and Job History • • 1. 2. 3. ©NIIT 2B.53 The details of each job can be viewed in the details pane of the Jobs container in SQL Server 2000 Enterprise Manager console. The following are the steps to view the properties and details of a job: In the details pane, click on any column name to sort the jobs based on the column name. Right-click the job and then click the Properties option, to open the Properties dialog box. Right-click the job and then click the View Job History option to review the history of a job execution. This will display the information regarding job execution, such as the day the job was run, who invoked the job, each time job was run, its result and the operators who are notified. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 25 of 31 Administering and Troubleshooting SQL Server 2000 Managing SQL Server 2000 Agent Jobs Reviewing SQL Server 2000 Jobs and Job History (Contd.) 4. 5. ©NIIT Select the Show Step details check box to display the details of execution of each step. The detailed step provides you information to troubleshoot a job. To control the size of the job history log, right-click the SQL Server Agent container, click Properties option, and then click the Job System tab. To delete the entire log, click the Clear Log button. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 26 of 31 The details of each job can be viewed in the details pane of the Jobs container in SQL Server 2000 Enterprise Manager console. The following are the steps to view the properties and details of a job: 1. Choose and expand the default instance, to reach the Management option. 2. Expand the Management option and choose the SQL Server Agent option. 3. Expand SQL Server Agent option and select the Jobs option to open the Jobs detail pane. 4. In the details pane, right-click a job to open the pop-up menu. Click the Properties option, to open the Properties dialog box, as shown. Administering and Troubleshooting SQL Server 2000 2B.54 5. Right-click the job and then click the View Job History option to review the history of a job execution. This will display the information regarding job execution, such as the day the job was run, the person who invoked the job, the time job was run, its result and the operators who were notified, as shown. 2B.55 Administering and Troubleshooting SQL Server 2000 6. Select the Show step details check box to display the details of execution of each step. The detailed step provides you information to troubleshoot a job, as shown. The following screen appears only after the task is executed. Administering and Troubleshooting SQL Server 2000 2B.56 7. 2B.57 To control the size of the job history log, right-click the SQL Server Agent container. Click the Properties option, and then click the Job System tab. To delete the entire log, click the Clear Log button. Administering and Troubleshooting SQL Server 2000 TROUBLESHOOTING TIPS Following are the troubleshooting tips that can help you to identify the problems related to the improper functioning of alerts, jobs, operators, or notifications: If for any reason SQL Server Agent has stopped and is unable to execute the defined jobs and alerts, then verify for the mapping of the login account of SQL Server Agent and SQL Server sysadmin role. In addition, you can also verify the login account password. If SQL Server Agent is unable to execute alerts and jobs as per the schedule and the operators do not receive notifications, then verify that the alert, job, schedule, or operators is active and enabled. If the job owner fails to execute the job steps, then verify that the job owner has sysadmin role permission to run the jobs. The job owner, in this case, should belong to the Windows domain account. You also view the properties of an alert, using the sp_help_alert system stored procedure of Transact-SQL. Administering and Troubleshooting SQL Server 2000 2B.58 INSTRUCTOR NOTES FAQs 1. Is it possible to view the properties of existing jobs? Ans: Yes, it is possible to view the properties of existing jobs, using the sp_help_job and sp_help_jobstep system stored procedures of Transact-SQL. 2. Is it possible to view the properties of existing alerts? Ans: Yes, it is possible to view the properties of existing alerts. Right-click the alert to display a pop-up menu to view the properties of the alert. Select the Properties option to display the alert’s Properties dialog box. The Properties dialog box displays the details of the specified alert. 3. Is it possible to execute a job when it is disabled? Ans: No, if a job is disabled, it will not execute in response to any alert or schedules. 2B.59 Administering and Troubleshooting SQL Server 2000 SUMMARY Managing SQL Server 2000 Agent Jobs Summary In this lesson, you learned: • SQL Server Agent service is used to monitor certain administrative tasks and server events that occur regularly. • The components of SQL Server Agent service are: • Alerts • Operators • Jobs • An alert is an event or error message that occurs in SQL Server and sent to the operators via e-mail, NET SEND, and pager. • You need to specify an alert to provide notification for events such as user-defined errors and for describing the performance condition. • An operator receives a message when an alert is fired. ©NIIT Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 27 of 31 Administering and Troubleshooting SQL Server 2000 2B.60 Managing SQL Server 2000 Agent Jobs Summary (Contd.) • • • • ©NIIT 2B.61 The operators can use the following messaging methods to send notifications: • E-mail • Pager • NET SEND You can define a new operator using SQL Server Enterprise Manager or by executing sp_add_operator system stored procedure. A job is a series of steps that are performed by the SQL Server Agent service. Using jobs, you can define schedules for the execution of task. SQL Server 2000 supports the following types of job steps: • Operating system commands or CMDExec commands • Transact-SQL statements • Microsoft ActiveX scripts • Replication tasks Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 28 of 31 Administering and Troubleshooting SQL Server 2000 Managing SQL Server 2000 Agent Jobs Summary (Contd.) • • • • • • ©NIIT You can configure a job step to perform multiple jobs sequentially on success or failure of a job process. A job process can also be configured to quit or report its success or failure. You can schedule a job to run continuously or at recurring intervals, such as hourly, daily, or weekly. You can also schedule a job to run only for a single time or in response to a defined alert. You can create a job using the Create Job wizard and SQL Server Enterprise Manager. Multi server jobs are used to automate jobs on multiple servers in a network. To automate jobs on multiple servers, you need to define one master server and one or more target servers. The master server is responsible for distributing jobs to the target servers. You need to specify an alert to provide notification for events such as user-defined errors and for describing the performance condition. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 29 of 31 Administering and Troubleshooting SQL Server 2000 2B.62 Managing SQL Server 2000 Agent Jobs Summary (Contd.) • • ©NIIT 2B.63 The main attributes of the SQL Server alerts and their messages are: • Error number • Message string • Severity • State code • Procedure name • Line number You can review job and alert history using the SQL Server 2000 Enterprise Manager. Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 30 of 31 Administering and Troubleshooting SQL Server 2000 Managing SQL Server 2000 Agent Jobs Summary (Contd.) • The following are the troubleshooting tips that can help you to identify the problems related to improper functioning of alerts, jobs, and operators: • If for any reason SQL Server Agent has stopped and is unable to execute the defined jobs and alerts, then verify for the mapping of the login account of SQL Server Agent and SQL Server sysadmin role. • If SQL Server Agent is unable to execute alerts and jobs as per the schedule and the operators do not receive notifications, then verify that the alert, job, schedule, or operators is active and enabled. • If the job owner fails to execute the job steps, then verify that the job owner has sysadmin role permission to run the jobs. The job owner, in this case, should belong to the Windows domain account. ©NIIT Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 31 of 31 In this lesson, you learned that: SQL Server Agent service is used to monitor certain administrative tasks and server events that occur regularly. The components of SQL Server Agent service are: x Alerts x Operators x Jobs An alert is an event or error message that occurs in SQL Server and sent to the operators via e-mail, NET SEND, and pager. You need to specify an alert to provide notification for events such as userdefined errors and for describing the performance condition. The main attributes of the SQL Server alerts and their messages are: x x x x Error number Message string Severity State code Administering and Troubleshooting SQL Server 2000 2B.64 x Procedure name x Line number An operator receives a message when an alert is fired. The operators can use the following messaging methods to send notifications: x E-mail x Pager x NET SEND You can define a new operator using SQL Server Enterprise Manager or by executing sp_add_operator system stored procedure. A job is a series of steps that are performed by the SQL Server Agent service. Using jobs, you can define schedules for the execution of task. SQL Server 2000 supports the following types of job steps: x Operating system commands or CMDExec commands x Transact-SQL statements x Microsoft ActiveX scripts x Replication tasks You can configure a job step to perform multiple jobs sequentially on success or failure of a job process. You can schedule a job to run continuously or at recurring intervals. You can create a job using the Create Job wizard and SQL Server Enterprise Manager. Multi server jobs are used to automate jobs on multiple servers in a network. To automate jobs on multiple servers, you need to define one master server and one or more target servers. The master server is responsible for distributing jobs to the target servers. You need to specify an alert to provide notification for events such as userdefined errors and for describing the performance condition. The main attributes of the SQL Server alerts and their messages are: x x x x x 2B.65 Error number Message string Severity State code Procedure name Administering and Troubleshooting SQL Server 2000 x Line number You can review job and alert history Manager. using the SQL Server 2000 Enterprise The following are the troubleshooting tips that can help you to identify the problems related to improper functioning of alerts, jobs, and operators: x If for any reason SQL Server Agent has stopped and is unable to execute the defined jobs and alerts, then verify for the mapping of the login account of SQL Server Agent and SQL Server sysadmin role. x If SQL Server Agent is unable to execute alerts and jobs as per the schedule and the operators do not receive notifications, then verify that the alert, job, schedule, or operators is active and enabled. x If the job owner fails to execute the job steps, then verify that the job owner has sysadmin role permission to run the jobs. The job owner, in this case, should belong to the Windows domain account. Administering and Troubleshooting SQL Server 2000 2B.66 [...]... Troubleshooting SQL Server 2000 2B.32 Managing SQL Server 2000 Agent Jobs Creating and Managing SQL Server 2000 Agent Jobs (Contd.) Export Database On Success On Failure Update Database Success Report Backup Database Failure Report ©NIIT 2B.33 Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 17 of 31 Administering and Troubleshooting SQL Server 2000 Managing SQL Server 2000 Agent Jobs Creating and Managing SQL. .. SERVER 2000 AGENT JOBS Managing SQL Server 2000 Agent Jobs Creating and Managing SQL Server 2000 Agent Jobs • • • ©NIIT Jobs can be defined as a set of tasks performed sequentially by SQL Server 2000 Agent services The action performed by jobs on database or server is known as job steps SQL Server 2000 supports job steps that can be: • Operating system commands or CMDExec commands • Transact -SQL statements... table Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 10 of 31 Administering and Troubleshooting SQL Server 2000 2B.14 Managing SQL Server 2000 Agent Jobs Introducing Alert (Contd.) • ©NIIT The following are the main attributes of the SQL Server alerts and their messages: • Error number • Message string • Severity • State code • Procedure name • Line number Managing SQL Server 2000 Agent Jobs... creating agent job using the SQL Server 2000 Enterprise Manager as a practice exercise Next, discuss about the multiserver jobs, its components, and the processing of multiserver jobs Then, discuss the steps to review the details of the existing jobs and job history using the SQL Server 2000 Enterprise Manager 2B.31 Administering and Troubleshooting SQL Server 2000 CREATING AND MANAGING SQL SERVER 2000 AGENT. .. be executed on one local server or multiple remote servers Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 9 of 31 SQL Server 2000 provides the SQLServerAgent service to programmatically administer certain administrative tasks or server events that occur regularly The SQLServerAgent service uses three components to accomplish this task They are: Alerts Operators Jobs Alerts An alert is an... performed by the SQL Server Agent services, sequentially You can schedule a job to run sequentially or at recurring intervals You can create a job using the Create Job wizard Working with Jobs Jobs can be defined as a set of tasks performed sequentially by SQL Server 2000 Agent services The action performed by jobs on database or server is known as job steps SQL Server 2000 supports job steps that can... using the SQL Server 2000 Enterprise Manager as a practice exercise Finally, discuss the steps to review the details of the existing alerts and alert history using SQL Server 2000 Enterprise Manager You can end the session by telling the students about troubleshooting SQL Server agents, jobs, and alerts 2B.13 Administering and Troubleshooting SQL Server 2000 CREATING AND MANAGING SQL SERVER 2000 AGENT. .. Managing SQL Server 2000 Agent Jobs (Contd.) • Jobs Scheduling: • You can schedule a job to run continuously or at recurring intervals, such as hourly, daily, or weekly • You can also schedule a job to run whenever SQL Server Agent starts or CPU utilization of a computer is idle • Each job schedule can be enabled or disabled ©NIIT Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 18 of 31 Jobs are... Scott who is designated as a fail-safe operator by SQL Server 2000 Administering and Troubleshooting SQL Server 2000 2B.24 Solution Managing SQL Server 2000 Agent Jobs Task List • • • • ©NIIT Configure Configure Configure Verify the operator details notification details fail-safe operator details operator configuration Managing SQL Server 2000 Agent Jobs Lesson 2B / Slide 15 of 31 To solve the preceding.. .Managing SQL Server 2000 Agent Jobs Introduction to SQLServerAgent Service (Contd.) • Jobs : • • • • ©NIIT A job is a series of steps that are performed sequentially by SQL Server Agent Using jobs, you can define schedules for the execution of task In addition, using jobs you can define the administrative task that can be monitored for