on 10th oct 01.30 pm pst, i will be speaking on “detect worst performing sql queries during peak hour” @ sqlsaturday, orlando!!, if you are in the area i hope to see you…

pass sqlsaturday’s are free 1-day training events for sql server professionals that focus on local speakers, providing a variety of high-quality technical sessions, and making it all happen through the efforts of volunteers and sponsors. whether you’re attending a sqlsaturday or thinking about hosting your own, i think you’ll find it’s a great way to spend a saturday – or any day.

sqlsaturday – orlando – 10 oct 2015

event schedule

session: detect worst performing sql queries during peak hour

register here

session feedback

scripts repository – github

session detail:

how many times you have been thrown in a situation when you have been asked to fix performance issues of a database system which you have never seen before? where do you start tuning? when do you stop tuning? each application is different. with the ever increasing number of systems one production dba has to manage today, it’s very important to use top to bottom approach to troubleshoot performance issues, which will lead to the answers in the right way for the application under consideration.

while you can find top queries, wouldn’t it be awesome if you can find out which ones are the exact queries taking most of the resources in last hour in current situation without using profiler or causing any additional load on system? now you can focus on those specific queries!

in these 60 minutes, prakash walks you through with scenario & demos to find which exact queries are taxing production systems resources based on cpu/disk/memory/network. they are all based on his own real-life experience from managing demanding database systems.

you’ll learn how to:

• detect worst performing sql queries which slows down microsoft sql server performance without using profiler

• key dmvs used to detect worst performing queries, along with various type of information available for those queries

• investigation workflow with which you will be able to pin point a specific stored procedure/query that is the cause of the performance problem faced.