Automating Administration with SQL Agent



Similar documents
Working with SQL Server Agent Jobs

Backups and Maintenance

SQL Server Automated Administration

System Area Management Software Tool Tip: Integrating into NetIQ AppManager

Using AppMetrics to Handle Hung Components and Applications

Video Administration Backup and Restore Procedures

Tool Tip. SyAM Management Utilities and Non-Admin Domain Users

How To Create An Easybelle History Database On A Microsoft Powerbook (Windows)

3 Setting up Databases on a Microsoft SQL 7.0 Server

Automated backup. of the LumaSoft Gas database

Outlook Profile Setup Guide Exchange 2010 Quick Start and Detailed Instructions

QUANTIFY INSTALLATION GUIDE

NETWRIX EVENT LOG MANAGER

STIDistrict Server Replacement

Microsoft SQL Server Staging

Moving the TRITON Reporting Databases

TSM for Windows Installation Instructions: Download the latest TSM Client Using the following link:

Getting to Know the SQL Server Management Studio

Installing Windows Server Update Services (WSUS) on Windows Server 2012 R2 Essentials

Migrating MSDE to Microsoft SQL 2008 R2 Express

Legal Notes. Regarding Trademarks KYOCERA MITA Corporation

Table of Contents. CHAPTER 1 About This Guide CHAPTER 2 Introduction CHAPTER 3 Database Backup and Restoration... 15

Introducing SQL Server Express

MadCap Software. Upgrading Guide. Pulse

Step-by-Step Guide to Setup Instant Messaging (IM) Workspace Datasheet

Printer Maestro. True Enterprise Print Management for Windows WHITE PAPER

Database Maintenance Guide

Deploying Remote Desktop Connection Broker with High Availability Step-by-Step Guide

Configuring WMI Performance Monitors

Exercise Safe Commands and Audit Trail

Nexio Connectus Cluster Set Up with SQL Server Backend

TSM Studio Server User Guide

Sophos Mobile Control Installation guide

File Management Utility User Guide

Sitecore Ecommerce Enterprise Edition Installation Guide Installation guide for administrators and developers

SonicWALL CDP 5.0 Microsoft Exchange InfoStore Backup and Restore

QAD Enterprise Applications. Training Guide Demand Management 6.1 Technical Training

DBMoto 6.5 Setup Guide for SQL Server Transactional Replications

Crystal Reports Installation Guide

Microsoft SQL Server 2008 Administrator's Pocket Consultant

1 of 10 1/31/2014 4:08 PM

Snow Inventory. Installing and Evaluating

ImageNow Cluster Resource Monitor

XStream Remote Control: Configuring DCOM Connectivity

Monitoring SQL Server with Microsoft Operations Manager 2005

SonicWALL CDP Local Archiving

Back Up and Restore. Section 11. Introduction. Backup Procedures

BUILDER 3.0 Installation Guide with Microsoft SQL Server 2005 Express Edition January 2008

Microsoft SQL Server Guide. Best Practices and Backup Procedures

SQL Tuning and Maintenance for the Altiris Deployment Server express database.

Using the Query Analyzer

Protecting SQL Server Databases Software Pursuits, Inc.

STATISTICA VERSION 10 STATISTICA ENTERPRISE SERVER INSTALLATION INSTRUCTIONS

Team Foundation Server 2010, Visual Studio Ultimate 2010, Team Build 2010, & Lab Management Beta 2 Installation Guide

NETWRIX CHANGE NOTIFIER

Erado Archiving & Setup Instruction Microsoft Exchange 2007 Push Journaling

PRODUCT WHITE PAPER LABEL ARCHIVE. Adding and Configuring Active Directory Users in LABEL ARCHIVE

Releasing blocked in Data Security

Table of Contents SQL Server Option

Cloud Services ADM. Agent Deployment Guide

Print Audit 6 - SQL Server 2005 Express Edition

SonicWALL CDP 5.0 Microsoft Exchange User Mailbox Backup and Restore

12 SPS DATABASE ADMINISTRATION

NETWRIX EVENT LOG MANAGER

Technical Paper. Defining an ODBC Library in SAS 9.2 Management Console Using Microsoft Windows NT Authentication

Administering and Managing Log Shipping

Connecting to Delta College Exchange services off-campus

NETWRIX USER ACTIVITY VIDEO REPORTER

Arkay Remote Data Backup Client Quick Start Guide

Lab: Data Backup and Recovery in Windows XP

Aventail Connect Client with Smart Tunneling

WhatsUp Gold v16.3 Installation and Configuration Guide

Configuration Task 3: (Optional) As part of configuration, you can deploy rules. For more information, see "Deploy Inbox Rules" below.

IMPORTANT: The person who installs and sets up the PCS Axis database on the central database server

Ascend Interface Service Installation

Exchange Outlook Profile/POP/IMAP/SMTP Setup Guide

Shasta College SharePoint Tutorial. Create an HTML Form

CONFIGURING TARGET ACTIVE DIRECTORY DOMAIN FOR AUDIT BY NETWRIX AUDITOR

Budget Developer Install Manual 2.5

Create, Link, or Edit a GPO with Active Directory Users and Computers

How to Replicate BillQuick 2003 database on SQL Server 2000.

Integrating LANGuardian with Active Directory

Installing GFI MailArchiver

Moving a Romexis Database to an Existing SQL Instance

MicrosoftDynam ics GP TenantServices Installation and Adm inistration Guide

SQL Server Replication Guide

Installation Guide v3.0

STIDistrict SQL 2000 Database Management Plans

SWCS 4.2 Client Configuration Users Guide Revision /26/2012 Solatech, Inc.

Xythos on Demand Quick Start Guide For Xythos Drive

Setting up a database for multi-user access

Immotec Systems, Inc. SQL Server 2005 Installation Document

Reconfiguring VMware vsphere Update Manager

SQL Database Administration. Overview

Lenovo Online Data Backup User Guide Version

Troubleshooting Failover in Cisco Unity 8.x

Moving the Web Security Log Database

Non-ThinManager Components

Configuring a Custom Load Evaluator Use the XenApp1 virtual machine, logged on as the XenApp\administrator user for this task.

EVault for Data Protection Manager. Course 301 Server Protection with DPM File and System State

Transcription:

Automating Administration with SQL Agent Automating Administration with SQL Agent Objectives Configure SQL Server Agent. Set SQL Server Agent properties. Configure a fail-safe operator. Create operators. Create jobs. Create alerts. Microsoft SQL Server 2000 Professional Skills Development 17-1

Automating Administration with SQL Agent Configuring SQL Server Agent SQL Server Agent is well-named it s responsible for automating all SQL Server administrative tasks. In order for SQL Server Agent to execute jobs and fire alerts, it must be running at all times. Its login account must be mapped to the sysadmin fixed server role, and its domain user account login must be a member of the Windows NT/Windows 2000 Administrators group. You should configure Agent to start automatically whenever Windows NT/Windows 2000 is started. You can do this by using the SQL Server Service Manager applet, as shown in Figure 1. Figure 1. Configuring SQL Server Agent to start when Windows starts up. You can also set SQL Server Agent to autostart from the Enterprise Manager by right-clicking on your server and choosing Properties from the menu. Make sure the Autostart SQL Server Agent option is checked. There are three components to the SQL Server Agent: Jobs are objects consisting of one or more operations, or steps, to be performed. Steps are defined as Transact-SQL statements and can be scheduled. Alerts are actions to be taken when specific events occur. Alerts can be set to react to errors or to other conditions. Alerts can be configured to send e-mail, to page an operator, or to run a job. Operators are people who are designated through their network account or e-mail ID to receive alerts through e-mail, a pager, or a net send network command. In addition, the SQL Server Agent can also be configured to work hand-inhand with the Windows Performance Monitor. You can set up jobs, alerts, and 17-2 Microsoft SQL Server 2000 Professional Skills Development

Configuring SQL Server Agent operators through Transact-SQL, but it s easier to use the Enterprise Manager. To view SQL Server Agent jobs, operators, and alerts expand the Mangement SQL Server Agent node in the Enterprise Manager, as shown in Figure 2. Figure 2. Viewing alerts, operators, and jobs in the Enterprise Manager. When you first install SQL Server, you won t have any jobs or operators, so those folders will be empty. However, SQL Server does ship with some predefined alerts, as shown in Figure 3. You can use these existing alerts and also add to them by creating your own custom alerts. Figure 3. Prebuilt alerts that ship with SQL Server. Microsoft SQL Server 2000 Professional Skills Development 17-3

Automating Administration with SQL Agent Setting SQL Server Agent Properties To set or revise properties for SQL Server Agent, right-click on the SQL Server Agent node and choose Properties from the menu. This will load the SQL Server Agent Properties dialog box shown in Figure 4. Use the General tab to designate the account that Agent runs under, and a MAPI mail profile for configuring SQL Mail. Figure 4. Configuring SQL Server Agent from the Enterprise Manager. 17-4 Microsoft SQL Server 2000 Professional Skills Development

Configuring SQL Server Agent Click the Advanced tab to configure Agent to auto restart if it stops unexpectedly. You can also use settings here to forward events to a different server and detect when the CPU is idle so that jobs can be executed during idle times (see Figure 5). Figure 5. Setting options for SQL Server Agent to restart, forward events to a different server, or perform operations during idle time. Microsoft SQL Server 2000 Professional Skills Development 17-5

Automating Administration with SQL Agent Click the Alert System tab to format pager e-mails and set up a fail-safe operator (see Figure 6). It s recommended that you always set up a fail-safe operator. If an operator defined for a particular alert can t be reached, then the fail-safe operator will be notified. That way alerts don t fall through the cracks because someone is unavailable or offline. Figure 6. Configuring pagers and setting up a fail safe operator. 17-6 Microsoft SQL Server 2000 Professional Skills Development

Configuring SQL Server Agent The Job System tab lets you configure the job history log and set the shutdown timeout interval (see Figure 7). By default only members of the sysadmin fixed server role can execute CmdExec and active scripting tasks. This option is important for security reasons because the SQL Server Agent service itself must run with administrative privileges. A user with these permissions could create a job and have it executed, in effect granting them access to all the resources on the server. Figure 7. Setting up job system properties. Microsoft SQL Server 2000 Professional Skills Development 17-7

Automating Administration with SQL Agent The Connection tab is where you set up which authentication mode SQL Server Agent uses (see Figure 8). The default is the account that was selected for the services to run under when you installed SQL Server. If you choose SQL Server authentication, you ll need to use a SQL Server login that is a member of sysadmin. Figure 8. SQL Server Agent uses NT authentication by default. The remaining sections in this chapter will show you how to set up jobs, create operators, and generate alerts. 17-8 Microsoft SQL Server 2000 Professional Skills Development

Operators Operators Creating operators is important because you ll need to have someone to send notifications to when you set up jobs. Try It Out! Follow these steps to create a new operator: 1. Expand the Management SQL ServerAgent node and right-click on Operators. Choose New Operator from the menu. 2. This will load the New Operator Properties dialog box, as shown in Figure 9. Fill in appropriate settings for the new operator. Click the Test button to verify that the operator receives the test message. Figure 9. Configuring an operator. Microsoft SQL Server 2000 Professional Skills Development 17-9

Automating Administration with SQL Agent 3. Click the Notifications tab (see Figure 10). This allows you to designate this operator to receive notification on any of the predefined alerts. You ll learn how to add your own alerts to this list later in the chapter. Figure 10. Setting up notifications. 4. Click Apply or OK when finished. 17-10 Microsoft SQL Server 2000 Professional Skills Development

Jobs Jobs Jobs consist of one or more tasks that SQL Server Agent runs as a unit. These tasks can be Transact-SQL commands, backup and replication tasks, or programs that the SQL Server agent executes. Jobs can be scheduled, and notifications sent to operators on the success or failure of the tasks in the job. There are two ways to create a new job: Right-click on the SQL Server Agent node in the Management folder and choose New Job from the menu. Run the Create Job Wizard. When you re first getting started, the easiest way to create a job is with the wizard. Once you re familiar with the different options, you can bypass the wizard and create new jobs manually. Try It Out! Follow these steps to create a job to check the consistency of the Shark database using the Create Job Wizard: 1. Select Tools Wizards Management Create Job Wizard from the menu in the Enterprise Manager main console. Microsoft SQL Server 2000 Professional Skills Development 17-11

Automating Administration with SQL Agent 2. Click Next on the introductory screen to move to the second wizard dialog box. Select the job type Transact-SQL command, as shown in Figure 11. The job in this case is Transact-SQL statement. Click Next to continue. Figure 11. Selecting the job type. 17-12 Microsoft SQL Server 2000 Professional Skills Development

Jobs 3. In the next wizard dialog box, type in the Transact-SQL statement DBCC CHECKDB, as shown in Figure 12. Click the Parse button to check your syntax. Note that you could open a script file if you had a saved script defining the job by clicking the Open button. Click Next. Figure 12. Checking the database. Microsoft SQL Server 2000 Professional Skills Development 17-13

Automating Administration with SQL Agent 4. The next wizard dialog box lets you set up a schedule for when you want the new job to run, as shown in Figure 13. Click the Schedule button to set up a schedule. Click OK and then Next when finished. Figure 13. Scheduling the job. 17-14 Microsoft SQL Server 2000 Professional Skills Development

Jobs 5. Figure 14 shows selecting an operator to be notified about the status of the job. Click Next when finished. Figure 14. Notifying an operator. 6. The final dialog box summarizes the choices you ve made and asks you to name the new job. Name it SharkConsistencyCheck and click the Finish button to create the job. Once you ve created the job, it will show up in the SQL Server Agent Jobs folder. You can modify the existing job by adding tasks or redefining existing ones. Try It Out! Follow these steps to modify the SharkConsistencyCheck job by adding a task to shrink the Shark database: 1. Right-click on the SharkConsistencyCheck job in the SQL Server Agent Jobs folder and choose Properties from the menu. 2. Click the Steps tab and click the New button to create a new task. This loads the New Job Step dialog box. Microsoft SQL Server 2000 Professional Skills Development 17-15

Automating Administration with SQL Agent 3. Type Shrink Database for the job step and type the following Transact-SQL statement in the Command text box, as shown in Figure 15. DBCC SHRINKDATABASE (Shark, 10) Figure 15. Adding a new step to shrink the Shark database by 10%. 17-16 Microsoft SQL Server 2000 Professional Skills Development

Jobs 4. This command will shrink the Shark database, leaving 10% free space. Click the Advanced tab and choose Quit the job reporting success from the On success action drop-down list box, as shown in Figure 16. Fill in a location for a text file so you can view the output. Select dbo in the Run as user drop-down listbox. Figure 16. Quit the job on the last step. Microsoft SQL Server 2000 Professional Skills Development 17-17

Automating Administration with SQL Agent 5. Click OK when finished. This will drop you back to the main Properties dialog box, as shown in Figure 17. You now need to modify Step 1, or the Shrink Database step will never happen because the Quit with success option is selected. Click on Step 1 and choose Edit from the menu. Figure 17. Both steps show Quit with success. 6. Click the Advanced tab and choose Go to next step from the On success action drop-down list box. Click OK and then click Apply or OK to save changes to the job. 7. To execute the job, right-click on SharkConsistencyCheck and choose Start Job from the menu. Once the job has completed, you can check the output by opening the SharkConsistencyCheck.txt file in Notepad. 17-18 Microsoft SQL Server 2000 Professional Skills Development

Alerts Alerts An alert is a reaction to a SQL Server event such as transaction logs becoming full or triggering an error of a certain severity. SQL Server ships with some predefined alerts, as shown earlier in this chapter in Figure 3. However, there are no responses associated with these alerts operators aren t being e-mailed or paged. Try It Out! Follow these steps to associate an alert with the Demo: Full tempdb alert: 1. Expand the Alerts node in the SQL Server Agent folder and doubleclick on Demo: Full tempdb. This opens the Properties dialog box for the alert. Microsoft SQL Server 2000 Professional Skills Development 17-19

Automating Administration with SQL Agent 2. Click the Response tab. Check the operators you want to be notified and type in any additional messages in the bottom pane, as shown in Figure 18. Note that you can also execute a job in response to the alert occurring. Click Apply or OK when finished. Figure 18. Setting up a response to an existing alert. Setting up a response activates the alert and causes something to be done about the condition that caused the alert. Alerts can also be generated by a Windows NT/Windows 2000 Performance Monitor threshold being reached. In short, alerts are a powerful tool for letting someone know when things are happening. Try It Out! Follow these steps to create a new alert using the Create Alert Wizard. 1. Select Tools Wizards Management Create Alert Wizard from the menu in the Enterprise Manager main console. Click Next to bypass the introductory dialog box. 17-20 Microsoft SQL Server 2000 Professional Skills Development

Alerts 2. Choose 017 Insufficient Resources from the drop-down list box, as shown in Figure 19. Click Next. Figure 19. Defining the alert. Microsoft SQL Server 2000 Professional Skills Development 17-21

Automating Administration with SQL Agent 3. The next dialog box allows you to narrow down your selection to a single database, or choose to fire the alert for all databases. Type in the error message, as shown in Figure 20, and click Next. Figure 20. Specifying the database and an error message. 17-22 Microsoft SQL Server 2000 Professional Skills Development

Alerts 4. You can then designate a job to execute, or operators to receive the error message, as shown in Figure 21. Figure 21. Notifying operators in an alert. Microsoft SQL Server 2000 Professional Skills Development 17-23

Automating Administration with SQL Agent 5. You can then specify an additional message to be sent to the operator in addition to the message previously defined, as shown in Figure 22. Figure 22. Creating an additional alert notification message. 17-24 Microsoft SQL Server 2000 Professional Skills Development

Alerts 6. The final wizard dialog box will summarize your choices, as shown in Figure 23. Click Finish to complete the alert. Figure 23. The final dialog box in the wizard summarizes your choices. Once the alert is created, it will show up in the Alerts folder. You can doubleclick it to change any of the settings as needed. Microsoft SQL Server 2000 Professional Skills Development 17-25

Automating Administration with SQL Agent Summary SQL Server Agent is responsible for automating all SQL Server administrative tasks. SQL Server Agent requires a Windows NT/Windows 2000 administrative domain account to run. SQL Server Agent consists of jobs, alerts, and operators. Jobs consist of tasks to be performed and can consist of one or more steps. Operators are people who can be notified about jobs and alerts. Alerts are responses to events and can include notifications or execute scripts. Jobs, alerts, and operators can be created from the Enterprise Manager or from the wizards. 17-26 Microsoft SQL Server 2000 Professional Skills Development

Alerts Questions 1. Where can you configure SQL Server Agent to start when the operating system starts? 2. What kind of domain account does SQL Server Agent require to run under Windows NT/Windows 2000? 3. Why is a fail-safe operator useful? 4. What is the easiest way to create a job, alert, or operator? 5. How can you edit a job, alert, or operator once it has been created? Microsoft SQL Server 2000 Professional Skills Development 17-27

Automating Administration with SQL Agent Answers 1. Where can you configure SQL Server Agent to start when the operating system starts? From the SQL Server Service Manager applet or from the Server Properties dialog box in the Enterprise Manager. 2. What kind of domain account does SQL Server Agent require to run under Windows NT/Windows 2000? An Administrative account 3. Why is a fail-safe operator useful? If an operator defined for a particular alert can't be reached, then the fail-safe operator will be notified. 4. What is the easiest way to create a job, alert, or operator? By using one of the wizards in the Enterprise Manager. 5. How can you edit a job, alert or operator once it has been created? By right-clicking or double-clicking on it in the Enterprise Manager to bring up its Properties dialog box. 17-28 Microsoft SQL Server 2000 Professional Skills Development

Alerts Lab 17: Automating Administration with SQL Agent Microsoft SQL Server 2000 Professional Skills Development 17-29

Lab 17: Automating Administration with SQL Agent Lab 17 Overview In this lab you ll learn how to create operators, jobs, and alerts. To complete this lab, you ll need to work through three exercises: Create an Operator Create a Job Create an Alert Each exercise includes an Objective section that describes the purpose of the exercise. You are encouraged to try to complete the exercise from the information given in the Objective section. If you require more information to complete the exercise, the Objective section is followed by detailed step-bystep instructions. 17-30 Microsoft SQL Server 2000 Professional Skills Development

Create an Operator Create an Operator Objective In this exercise, you ll create an operator and assign them to receive notification when the msdb log is full and when tempdb is full. Things to Consider How do you create an operator? How do you contact the operator? How do you assign an alert to an operator? Step-by-Step Instructions 1. Right-click on the Operators node in the SQL Server Agent Operators folder and select New Operator from the menu. This loads the New Operator Properties dialog box. 2. Fill in the appropriate settings for the new operator. Click the Test button to verify that the operator receives the test message. Microsoft SQL Server 2000 Professional Skills Development 17-31

Lab 17: Automating Administration with SQL Agent 3. Click the Notifications tab. Select the Demo: Full msdb log and Demo: Full tempdb and click the Net Send checkboxes, as shown in Figure 24. Figure 24. Configuring a new operator. 4. Click Apply or OK to create the new operator. 17-32 Microsoft SQL Server 2000 Professional Skills Development

Create a Job Create a Job Objective In this exercise, you ll create a job to run the DBCC CHECKCATALOG on the Shark database to check the consistency of the systems tables in Shark. Things to Consider How do you create a job? How do you execute DBCC commands in a job? Step-by-Step Instructions 1. Right-click on Jobs in the SQL Server Agent Jobs node and select New Job from the menu. This loads the New Job Properties dialog box. 2. Type the name Shark System Check and click the Steps tab. 3. Click the New button to load the New Job Step dialog box. For the step name, type in Check System Tables and choose the Shark database from the drop-down list. Type the following Transact-SQL statement in the Command box: DBCC CHECKCATALOG ('Shark') 4. Click the Parse button and then click the Advanced tab. Microsoft SQL Server 2000 Professional Skills Development 17-33

Lab 17: Automating Administration with SQL Agent 5. Fill in the options shown in Figure 25 to quit on success, and create an output file named AgentLab.txt in a folder on your hard drive. Select dbo in the Run as user drop-down listbox. Click OK when finished. Figure 25. Configure the job to create an output file. 6. Click OK. This saves the job. To execute the job, right-click and choose Start Job from the menu. Click Start to run the job. 7. After the job has completed running, open AgentLab.txt in Notepad. The contents should look like the following: Job 'Shark System Check' : Step 1, 'Check System Tables' : Began Executing 2000-10-20 18:15:33 DBCC results for 'Shark'. [SQLSTATE 01000] DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000] 17-34 Microsoft SQL Server 2000 Professional Skills Development

Create an Alert Create an Alert Objective In this exercise, you ll create an alert for a fatal hardware error. If a fatal hardware error triggers the alert, the operator you created in the first exercise will be notified. Things to Consider How do you create an alert? How do you notify an operator? Step-by-Step Instructions 1. Right-click the Alerts node in the SQL Server Agent Alerts folder and choose New Alert from the menu. This loads the New Alert Properties dialog box. Microsoft SQL Server 2000 Professional Skills Development 17-35

Lab 17: Automating Administration with SQL Agent 2. Fill in Hardware Error for the name and select 024 Fatal Error: Hardware Error from the Severity drop-down listbox. Type A fatal hardware error has occurred. for the error message text, as shown in Figure 26. Figure 26. Defining the alert. 3. Click the Response tab. Select the operator you created in the first exercise and click the Net-Send checkbox. Click Apply or OK. 17-36 Microsoft SQL Server 2000 Professional Skills Development