Mehedi's Earth

In Part-1 we discussed, about the basic concepts of wait stat and in Part-2 we checked how to find out blocked queries, analysis of historical data, CPU pressure and primary resource waits. In this final part, you will see the common wait types, and check how to create baseline for wait stat. Let's deep drive! [More]

In part-1, we explored the basics of SQL Server Wait Statistics—what they are, how they work, and how to gauge. Now it is time to put that knowledge into action. In this part, you are going to use wait stats as a powerful tool to diagnose performance bottlenecks and guide your tuning efforts.

Think of wait stats as your server’s way of telling you where it is struggling—whether it is waiting on disk I/O, locking issues, or just CPU pressure. By learning to read these signals, you will be able to focus your optimization efforts where they matter most and keep your SQL Server running smoothly. [More]

When SQL Server slows down, it is not always easy to figure out why. That is where Wait Statistics come into play — they act like a performance stethoscope, helping DBAs listen to what SQL Server is waiting on. Every query, every process, leaves behind clues in the form of waits. By understanding these waits, you can diagnose bottlenecks, uncover hidden issues, and fine-tune your server for peak performance.

In this series, I will tell you some relevant concepts, show you how to read them, and help you decide what actions to take — so you are not just guessing anymore. [More]

When it comes to query performance tuning in SQL Server, key lookups are often the silent culprits that slow things down. This seemingly small operation can become expensive when repeated over thousands—or millions—of rows. In this article, we will break down what a key lookup is, why it happens, and how you can eliminate it with smarter indexing strategies. By addressing key lookups, you can significantly reduce I/O and boost query speed. So grab your execution plan and let’s uncover the hidden costs! [More]