Having worked on development teams for years, this is something that I have heard more times than I can count. A developer believes bad performance is caused by the infrastructure and an Admin believes that bad performance is caused by the code, but whose right? The answer is it could be either one or a combination of both, but you have to know where to look.

In this session, I will show you how you can use server wait stats in SQL Server to provide insight into why your servers may be running slow. We will start by looking at what role server resources (CPU, Memory, Network and Disks) play in the big picture of query processing and show you how you can use server wait stats to identify bottlenecks with each of these. We will also review common server waits that can occur at each crossroads of a query, reasons you may be having them and what you can do to solve the problem. Being able to look at the wait stats and interpret the results should assist you in answering the question of is it the server or the code, or both!

The goal for this session is that you walk away with a better understanding of what wait stats are and how you can put them to use immediately to figure out your performance issues.