My question just got published at DBA Quiz 2011. This question is inspired from a real life incident, which occurred to me a few years ago. That time, I was a DBA myself and then one fine day, everything went south. When we checked the log, all the logs were fine till few minutes before our server started to face the issue. After working for long hours, we fixed the issue. Our CTO had called us to analyze the situation. Instead of blaming anyone, he adorned an extremely positive attitude. He suggested that we all go out and come back with three top best solutions. We all gathered after a week and looked at each other’s solution. We combined that and put them in order for our later reference.
Well, today we are going to do the same task. SQL Server MVP Jacob Sebastian has come up with an SQL Server DBA Quiz where my question has just got published.
A query that was working fine every time suddenly became slow. There has been no change in the workload; no new development changes have been deployed, and there have been no other configuration changes in the system. Everybody runs to the DBA asking for resolution. If you were the DBA, what will be the first thing you would do and why? List the three most important priorities.
There are various awards for the winner, but here is a small effort from me. Irrespective of the whoever wins the SQL Quiz at the end, I will give a copy of my wait stats print book to one person who has attempted to answer the question I have asked. If you are not sure on how to answer this question, here is a quick hint.
Reference: Pinal Dave (http://blog.SQLAuthority.com)