Skip to content

Latest commit

 

History

History
42 lines (23 loc) · 3.05 KB

readme.md

File metadata and controls

42 lines (23 loc) · 3.05 KB
Raw

Special Edition Module for Performance Troubleshooting

This is a special edition module for performance troubleshooting. This module is intended to be used as advanced module and take after going through all the other 6 modules for the Azure SQL Workshop.

The scripts in this module accompany the Azure SQL for Beginners Special Edition on Performance Troubleshooting: https://aka.ms/azuresql4beginners

Prerequisites

Each module describes the specific setup required but to go through these examples you will need at minimum:

  • An Azure subscription with rights to create an Azure SQL Database. Most scenarios use a General Purpose Service Tier Azure SQL Database with 2 vCores. One scenario will require you to scale the database to 20 vCores.
  • A client computer that has network connectivity to connect to an Azure SQL Database
  • SQL Server Management Studio (SSMS) which you can download from https://aka.ms/ssms19. A working knowledge of SSMS will be helpful for these exercises. Use the following quickstart to learn how to use SSMS with Azure SQL: https://learn.microsoft.com/en-us/sql/ssms/quickstarts/ssms-connect-query-azure-sql
  • The client stress tool ostress.exe which you can download from https://aka.ms/ostress

Performance Troubleshooting Scenarios

This module contains the following scenarios which can be taken independent of each other:

High CPU due to a missing index

This scenario involves a performance problem seen by high CPU due to a missing index for a query. To go through this scenario, follow the instructions in the highcpu_missingindex folder.

High CPU due to antipattern queries

This scenario involves a performance problem seen by high CPU due to an antipattern query. To go through this scenario, follow the instructions in the highcpu_antipattern folder.

High CPU due to lack of resources

This scenario involves a performance problem seen by high CPU due to lack of CPU resources. To go through this scenario, follow the instructions in the highcpu_lackofresources folder.

Waiting due to blocking

This scenario involves a performance problem seen by little or no CPU resources but performance is slow due to a blocking problem between different SQL requests. To go through this scenario, follow the instructions in the waiting_blocking folder.

Waiting due to deadlocks

This scenario involves a performance problem seen by little or no CPU resources but performance is slow due to deadlocks between different SQL transactions. To go through this scenario, follow the instructions in the waiting_deadlocks folder.

Waiting due to memory grants

This scenario involves a performance problem seen by some or low CPU but performance is slow due to a high need for memory grants for several SQL concurrent queries. To go through this scenario, follow the instructions in the waiting_memorygrant folder.