SQL Server Performance Tuning

How We Made T-SQL Queries Run 51 Times Faster

Updated October 29, 20253 min read

From index scan to seek: 51x faster. A big horseshoe magnet pulls a single needle out of a haystack.

Improvement after tuning

51xDURATION
66xCPU
59xDISK

Reading from the disk is the slowest operation in SQL Server.

Thus, optimizing for fewer disk reads is often the target.

Problem

The stored procedure was continuously involved in deadlocking due to an index scan operation.

Pre-tuning Metrics

8,656
Duration (ms)
60,663
CPU (ms)
313,137
Disk (number of reads)

Solution

By adding a new index, we can turn a scan operation into a seek, making it much more efficient.

Before vs. After

The improvement was huge: the total number of disk reads dropped from 313,137 to just 5,337!

That's 59x!

As you can see in the chart below, CPU time dropped even further - by almost 66 times.

Duration (ms)

66,663
Before tuning
922
After tuning

Here is a more detailed breakdown:

BeforeAfterImprovement (%)Improvement (x)
Duration (ms)*8,6561715,06251
CPU (ms)*60,6639226,58066
Disk, number of reads*313,1375,3375,86759
*The numbers are an average of multiple T-SQL runs

Overall, we observed a remarkable improvement, with the query execution becoming 51 times faster!

Final thoughts

The most common bottleneck for SQL Servers is disk access (or disk "reads").

It's neither the CPU nor the RAM, which are usually the first suspects for most customers.

And that makes much sense. Here is why:

  • Inefficient queries scan (or read) much data.
  • Data read in is stored in RAM. As more data is read in, “older” data is pushed out from RAM.
  • If there isn’t enough RAM to keep ALL data in memory (which is often not possible), SQL Server has to read from disk – and that is the slowest operation SQL Server can do.
  • When the query can be tuned to read 10 rows vs. 10 million – less CPU and RAM automatically are necessary.

Disk resources are the cause of 95% of SQL Server bottlenecks, so reducing the disk reads is usually the primary objective.

For the end-user, nothing is more crucial than the speed (or duration) of the query, in every case.

Tuning to reduce CPU/RAM resources is helpful too.

When queries are tuned to need less CPU & RAM, it means that the same server now has more capacity.

Check Red9's SQL Server Services

SQL Server Consulting

Perfect for one-time projects like SQL migrations or upgrades, and short-term fixes such as performance issues or SQL remediation.

Discover More ➜

SQL Server Managed Services

Continuous SQL support, proactive monitoring, and expert DBA help with one predictable monthly fee.

Discover More ➜

Emergency SQL Support

Take the stress out of emergencies with immediate access to a SQL Server Sr. DBA 24x7x365

Discover More ➜

Explore All Services ➜