Module 13 Automating SQL Server 2008 R2 Management

Module Overview Automating SQL Server Management Working with SQL Server Agent Managing SQL Server Agent Jobs

Lesson 1: Automating SQL Server Management Benefits of Automating SQL Server Management Available Options for Automating SQL Server Management Overview of SQL Server Agent Demonstration 1A: SQL Server Agent

Benefits of Automating SQL Server Management Reduced administrative workload Automate and Schedule regular tasks Proactive management Monitor Performance Recognize and respond to potential problems

Available Options for Automating SQL Server Management Jobs to perform regular tasks Alerts to respond to Events Operators to send Notifications from Jobs and Alerts

Overview of SQL Server Agent Runs as a Windows service Must be running to  Execute jobs  Fire alerts  Contact operators Start Mode should be set to Automatic SQL Server Agent is the component of SQL Server that is responsible for automation

Demonstration 1A: SQL Server Agent In this demonstration, you will see:  How to configure SQL Server Agent  How to review SQL Server Agent jobs using PowerShell

Lesson 2: Working with SQL Server Agent Defining Jobs, Job Step Types and Job Categories Creating Job Steps Scheduling Jobs for Execution Scripting Jobs Demonstration 2A: Scripting Jobs

Defining Jobs, Job Step Types and Job Categories Jobs support many types including: Transact-SQL Command line application PowerShell script execution Jobs can be configured to: Run once or repeatedly Start at SQL Server Agent start-up Start manually Jobs can be assigned to a Category SQL Server Agent Jobs are a specified series of operations performed sequentially by SQL Server Agent

Creating Job Steps Fail? Yes No Write to Application Log Fail the job Job step 1: Back up Database (Transact-SQL) Job step 2: Transfer Data (CmdExec) Job step 3: Custom Application (PowerShell) Yes Job succeeded Notify operator Job succeeded Notify operator No Fail? Notify operator

Scheduling Jobs for Execution Job: Backup Transaction Log Schedule: Mon-Sun Shift 1 Every 1 Hours From: 8:00 A.M. To: 5:00 P.M. Every 1 Hours From: 8:00 A.M. To: 5:00 P.M. Daily Schedule Schedule: Mon-Sun Shift 2 Every 4 Hours From: 5:01 P.M. To: 7:59 A.M. Every 4 Hours From: 5:01 P.M. To: 7:59 A.M. Daily Schedule More than one schedule can be defined per job Schedules can be reused in other jobs More than one schedule can be defined per job Schedules can be reused in other jobs

Scripting Jobs Jobs can be scripted for documentation, archiving, and deployment on other instances

Demonstration 2A: Scripting Jobs In this demonstration you will see how to:  Create a job in SSMS  Script a Job  Deploy a job on a second instance of SQL Server

Lesson 3: Managing SQL Server Agent Jobs Viewing Job History Querying SQL Server Agent-related System Tables and Views Troubleshooting Failed Jobs Demonstration 3A: Viewing Job History and Resolving Failed Jobs

Viewing Job History SQL Server Agent keeps history information in msdb Job history can be queried directly or viewed through SSMS Job Activity monitor shows current live information Retention of history can be configured based on time or size

Querying SQL Server Agent-related System Tables and Views SQL Server Agent keeps configuration and history in msdb  System tables for Agent are located in the dbo schema  Tables are documented in Books Online Use history tables to automate collection of job history over several systems SELECT j.name, jh.run_date, jh.run_time, jh.message FROM msdb.dbo.sysjobhistory AS jh INNER JOIN msdb.dbo.sysjobs AS j ON jh.job_id = j.job_id WHERE jh.step_id = 0; GO; SELECT j.name, jh.run_date, jh.run_time, jh.message FROM msdb.dbo.sysjobhistory AS jh INNER JOIN msdb.dbo.sysjobs AS j ON jh.job_id = j.job_id WHERE jh.step_id = 0; GO;

Troubleshooting Failed Jobs If SQL Server Agent is not running  Check settings of the service  Check the msdb database Review job history  Check job outcome to identify the last step that was executed  Check job step outcome to identify why the step failed If the job did not start, verify:  Job is enabled  Job is scheduled  Schedule is enabled Verify that all dependent objects such as databases, files, procedures are available  Check that security settings allow access to dependent objects

Demonstration 3A: Viewing Job History and Resolving Failed Jobs In this demonstration, you will see:  A job that has failed to execute correctly  How to review the job history using SSMS  How to review the job history using T-SQL

Lab 13: Automating SQL Server Management Exercise 1: Create a Data Extraction Job Exercise 2: Schedule the Data Extraction Job Challenge Exercise 3: Troubleshoot a Failing Job (Only if time permits) Logon information Estimated time: 45 minutes

Lab Scenario There are a number of routine tasks to be performed on the Proseware instance. Previously these tasks have been performed manually and the lack of consistency in performing these tasks has caused issues for the organization. On the new instance, you need to automate these tasks using SQL Server Agent. There is also a report about an existing SQL Server Agent job that is not performing as expected. If you have time, you need to resolve the issues with the job.

Lab Review How do you configure SQL Server Agent to notify you that a particular job has failed? Can one job include different types of job steps?

Module Review and Takeaways Review Questions Best Practices