Check Top Logical Reads Queries in 45 Seconds. From Symptoms to Root Clause. The "45 Seconds DBA Series" – What Real DBAs Check First | Part 8 🥇"

Before we dive into today's topic, if you missed my previous post you can take a look at SQL Server Management Studio 22.5.2 NEWS!.
👉 If you found this deep-dive helpful, feel free to check out the ads—your support helps me keep creating high-quality SQL Server content for the community.

If CPU usage is just the smoke, Logical Reads are the fire. In this post, I’ll show you how to identify the I/O-heavy queries that are silently starving your Buffer Pool and killing your Page Life Expectancy in under 45 seconds.

✔️ Memory Churn: High logical reads mean your queries are scanning massive amounts of data in the Buffer Pool. 🛠️
✔️ The 8KB Rule: Every logical read is an 8KB page access; 1 million reads equals roughly 7.6GB of data processed in memory. 📦
✔️ Plan Cache Mining: We use sys.dm_exec_query_stats to find the heaviest I/O hitters without the overhead of Extended Events. 🚀
✔️ Surgical Fixes: Moving from an Index Scan to an Index Seek can reduce logical reads from thousands to single digits. ✔️

Hi SQL SERVER Guys,

While most DBAs obsess over CPU spikes, the veterans look at Logical Reads. Why? Because high logical reads are the primary driver of high CPU and memory pressure. If your queries are forcing SQL Server to traverse millions of pages just to return ten rows, you aren't dealing with a hardware bottleneck—you're dealing with a design flaw. Let's find the truth in 45 seconds...

What It Really Is: Memory-Based I/O

A Logical Read occurs every time SQL Server fetches a page from the Buffer Pool (memory). If the page isn't in memory, it performs a Physical Read to bring it in.

💣 The Problem: Even if your data is "all in RAM," logical reads are not free. Each read requires a CPU cycle and a memory bus operation. High logical reads lead to "Buffer Cache Hit Ratio" illusions—you might have a 99% hit ratio, but your Page Life Expectancy (PLE) is tanking because a single poorly written query is flushing the cache repeatedly.

  • ⭐ Total vs. Average: A query running once with 1 million reads is bad, but a query running 10,000 times with 5,000 reads is a server-killer.

  • ⭐ Plan Cache DMVs: These provide a historical view of what has been running since the last service restart.

🧪 The 45-Second Investigation Script

Run this query to immediately see the top 10 queries causing the most memory pressure on your system:

SELECT TOP 10
    SUBSTRING(st.text, (qs.statement_start_offset/2) + 1,
    ((CASE statement_end_offset 
        WHEN -1 THEN DATALENGTH(st.text) 
        ELSE qs.statement_end_offset END 
            - qs.statement_start_offset)/2) + 1) AS [Query Text],
    qs.execution_count,
    [Avg Logical Reads] = qs.total_logical_reads / qs.execution_count,
    [Total Logical Reads] = qs.total_logical_reads,
    qs.total_worker_time / 1000 AS [Total CPU ms],
    qp.query_plan
FROM sys.dm_exec_query_stats AS qs
CROSS APPLY sys.dm_exec_sql_text(qs.sql_handle) AS st
CROSS APPLY sys.dm_exec_query_plan(qs.plan_handle) AS qp
ORDER BY qs.total_logical_reads DESC;

*Refer to the official Microsoft documentation for deep details on sys.dm_exec_query_stats metrics.

🚀 My REAL Strategy

During years of experience, I’ve found that 80% of high logical reads come from residual predicates. This is when SQL Server seeks to a point in an index but then has to read (scan) thousands of extra pages because the subsequent filters aren't part of the index.

  • Check for Scans: If your logical reads are high, look at the execution plan for "Index Scan" or "Table Scan". A scan of a 1GB table will always result in ~128,000 logical reads.
  • Look for Key Lookups: If a query has high logical reads but the execution plan shows a Seek, check for a Key Lookup. This is a common performance killer where SQL has to jump back to the clustered index for every single row.
  • SARGability is King: Functions on columns in the WHERE clause (e.g., WHERE LEFT(LastName, 1) = 'B') prevent index seeks and explode your logical read counts.

Related Posts

📢 Support the Blog: Did you find this deep-dive helpful? The ads you see here are selected to reflect your interests. If a partner's offer catches your eye, give it a look! Your engagement helps me continue publishing premium SQL Server content for the community.

Biondi Luca @2026 - Sharing over 25 years of Gained Knowledge for Passion. Share if you like my posts!

Comments

Post a Comment

I Post più popolari

Speaking to Sql Server, sniffing the TDS protocol

Image
Hello friends!  If yesterday you read my post and found it definitely boring (for the topic of course and not for how it was written to the author 😁) well today I promise you that the topic will be much more interesting! Let's talk about Sniffing , let's talk about going to see what happens when we "log in" or when we send a Query to SQL Server.  We will do this by taking a look to the little known tabular data stream (TDS) protocol built on top of the TCP/IP protocol. Ready! The TDS protocol What is the Tabular data stream (TDS) protocol?  The TDS is the protocol used by the SQL Server client Net-Library to communicates with SQL Server . TDS is specific to SQL Server and it is a low-level protocol that specifies both commands and data in a specific arrangement.  TDS encapsulate the TCP/IP protocol. Sniffing TDS packets you can read from the network the requests that your application do to the SQL Server and read the answer .   How to Sniff data from the ne...
Read more

SQL Server, find text in a Trigger, Stored Procedures, View and Function. Two ways and what ways is better

Image
Hi guys, Welcome back! Today a light post about a question that has been asked to me several times. The question is: how to  search for text inside a trigger or a stored procedure ? We have two different ways. A first way using a system view called syscomments: SELECT obj.xtype, text , * FROM sysobjects obj JOIN syscomments com on obj.id = com.id WHERE TEXT like '%text_that_i_am_searching_for%' A second way using a system view called sql_module: SELECT o. name AS Object_Name, o. type_desc , m. definition FROM sys.sql_modules m JOIN sys.objects o ON m. object_id = o. object_id WHERE m. definition Like '%text_that_i_am_searching_for%' ;   Another question is? What differences do we have in using one way instead of the other? Which solution is better? You have to consider that the system view sys.syscomment is obsolete and will be removed sooner or later. So don't use it in production enviroiments. The sys.sql_m...
Read more

SQL Server, Avoid that damn Table Spool!

Image
Hi guys, Welcome back for another post! A light one inspired from what i do during my work: many times I optimize queries rewriting them or adding index and i like it very much! Sometimes you need to use a little imagination, but everything you learn ... sooner or later it will come in handy! Enjoy the reading mates! Avoid the Table Spool, when you can A few days ago I came across a query whose execution time was very high ... or so it was for the client complaining about the problem. Before recreating it, let's create the structures and fill the tables with some data Create table PriceList (Id int identity (1,1) primary Key ,Code Varchar (20)) Insert into PriceList (code) select top 1000 right( '0000' + cast ( row_number () over ( order by id) as varchar (4)),4) from artico Insert into PriceList (code) select top 4000 right( '1000' + cast ( row_number () over ( order by id) as varchar (4)),4) from artico Create table OrdersList (Id int identity...
Read more