Knowledge United

Introduction:

The purpose of this two-day workshop 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.

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.

At Course Completion:

After completing this course, students will be able to:

• Define and implement monitoring standards for database servers and instances.
• Troubleshoot database server and database performance issues.
• Optimize the query performance environment.
• Troubleshoot SQL Server connectivity issues.
• Troubleshoot SQL Server data issues.
• Troubleshoot SQL Server concurrency issues.

Prerequisites:

Before attending this course, students must have:

• Working knowledge of SQL Server 2005 architecture including indexing, SQL execution plans, and SQL Server basic configuration.
• 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.
• Familiarity with SQL Server 2005 features, tools, and technologies.
• Microsoft Certified Technology Specialist: Microsoft SQL Server 2005 credential or equivalent experience.

It is recommended, but not required, that students have completed:

• Course 2778: Writing Queries Using Microsoft SQL Server 2005 Transact-SQL.
• Course 2779: Implementing a Microsoft SQL Server 2005 Database
• Course 2780: Maintaining a Microsoft SQL Server 2005 Database

Microsoft Certified Professional Exams

This course will help the student prepare for the following Microsoft Certified Professional exams:

• 70-444, Optimizing and Maintaining a Database Administration Solution by Using Microsoft SQL Server 2005

Student Materials:

The course materials are yours to keep. The student kit includes a comprehensive workbook and other necessary materials for this class.

Course Outline

Unit 1: Building a Monitoring Solution for SQL Server Performance Issues

• This unit provides an opportunity to the student to build a monitoring solution that will help to identify SQL Server performance issues. Students will use the tool provided to 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.
• Lab: Building a Monitoring Solution for SQL Server Performance Issues

Unit 2: Troubleshooting Database and Database Server Performance Issues

• This unit provides an opportunity for the students to troubleshoot SQL Server performance issues. Students analyze the sample monitoring output to determine the issue. This unit includes 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 the SQLdiag Tool Can Be Used to Analyze Outputs.
• Lab: Troubleshooting Database and Database Server Performance Issues

Unit 3: Optimizing the Query Performance Environment

• This unit gives an opportunity to the student 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 bad performing queries and directed to investigate possible reasons.
• The Methodology of Optimizing a Query Environment.
• The Query Performance Troubleshooting Process.
• Use of Database Tuning Advisor to Troubleshoot the Query Environment.
• Lab: Optimizing the Query Performance Environment

Unit 4: Troubleshooting SQL Server Connectivity Issues

• This unit explains the troubleshooting of common SQL Server problems. Examples include DNS issues, network authentication issues, and SQL Server 2005 endpoint issues.
• The Methodology of Troubleshooting SQL Server Connectivity Issues.
• Areas to Troubleshoot for Common Connectivity Issues.
• What Are SQL Server 2005 Endpoints?
• Lab: Troubleshooting SQL Server Connectivity Issues

Unit 5: Troubleshooting SQL Server Data Issues

• This unit lets students troubleshoot issues at a data level. One exercise will be used to identify a torn page as well as to recover the torn page. The second exercise will be a business unit report which contains invalid data. The goal will be 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.
• Lab: Troubleshooting SQL Server Data Issues

Unit 6: Troubleshooting SQL Server Data Concurrency Issues

• This module lets the students identify the offending objects that cause concurrency issues. The first exercise shows how to determine stored procedures involved in a deadlocked situation. The second exercise shows students how to determine the source of a blocking issue and the third exercise will show students how to evaluate wait types and latches.
• The Methodology of Troubleshooting Concurrency Issues.
• What Are SQL Server Latches?
• Activity: Choosing a Blocking Monitoring Solution
• Lab: Troubleshooting SQL Server Data Concurrency Issues