Synopsis

Please note that this course has been retired and is no longer available. Please see the Microsoft SQL Server 2005 page for courses currently available in this subject area.

The purpose of this two-day M2790 course is to teach database administrators working in enterprise environments how to determine and troubleshoot performance issues using Microsoft SQL Server 2005. The primary focus of this workshop is to teach the overall process of troubleshooting. It includes establishing monitoring standards and baselines, determining performance thresholds, and focusing the investigation on specific issues.

Intended Audience

This course is intended for current professional database administrators who have three or more years of on-the-job experience administering SQL Server database solutions in an enterprise environment.

Course Prerequisites

Before attending this M2790 training course, students should have the following prerequisites:

Basic monitoring and troubleshooting skills. For example, students should have used Sysmon and Perfmon on the job

Working knowledge of the operating system and platform. Students should understand how the operating system integrates with the database, what the platform or operating system can do, and the interaction between the operating system and the database

Basic understanding of server architecture such as CPU and memory utilization and disk input/output (I/O)

Basic knowledge of application architecture. Students should know how applications can be designed in three layers, what applications can do, the interaction between applications and the database, and the interaction between the database and the platform or operating system

Understanding of Transact-SQL syntax and programming logic

Basic knowledge of Microsoft Windows networking. Students should understand how Domain Name Service (DNS) operates and how servers communicate between domains

Schedule

This course has been retired and is no longer available.

Outline Course Contents

Building a Monitoring Solution for SQL Server Performance Issues

This unit provides an opportunity for the student to build a monitoring solution that will help to identify SQL Server performance issues. Students will design a baseline performance monitoring solution.

Narrowing Down a Performance Issue to an Environment Area

Guidelines for Monitoring Database Servers and Instances by Using Profiler and Sysmon

Guidelines for Auditing and Comparing Test Results

Troubleshooting Database and Database Server Performance Issues

This unit provides an opportunity for students to troubleshoot SQL Server performance issues. Students analyze the sample monitoring output to determine the issue. This unit includes information on a new feature in SQL Server 2005 which allows students to automatically sync a Sysmon log and Profiler trace. It also allows students to load and perform analysis against a Profiler trace using SQL Server queries. Finally, it allows students to run SQLdiag.exe as an additional troubleshooting tool.

Narrowing Down a Performance Issue to a Database Object

How Profiler Can Help Narrow a Search to a Specific Issue

How the SQLdiag Tool Can Be Used to Analyze Outputs

Optimizing the Query Performance Environment

This unit gives students an opportunity to determine the database-level reasons for poor query performance, like bad indexes and outdated index column statistics. Students are provided with samples from a Profiler trace or a listing of poorly performing queries and directed to investigate possible reasons

Troubleshooting SQL Server Data Issues

This unit lets students troubleshoot issues at a data level. One exercise will be used to identify and recover a torn page. The second exercise is a business unit report which contains invalid data. The goal is for the Database Administrator to track down the reasons for the invalid data.

The Methodology of Troubleshooting SQL Server Data Issues

The Process of Troubleshooting Data Integrity Issues

How Torn Pages Can be Resolved Using a Single-Page Restore

Troubleshooting SQL Server Data Concurrency Issues

This module lets the students identify the offending objects that cause concurrency issues. The first exercise shows students how to determine stored procedures involved in a deadlocked situation. The second exercise shows students how to determine the source of a blocking issue. The third exercise shows students how to evaluate wait types and latches.