SQL SERVER 2025, Why Your SQL Query Is Burning CPU (And You Don’t See It)

Why Your SQL Query Is Burning CPU (And You Don’t See It) 🔥

Hi SQL Server Guys,

👉 If you missed my previous post, check it out here:
SQL Server: Stop Defragmenting! The Auto Index Compaction Feature That Changes Everything

Your query is slow.
You check IO.
Everything looks fine.

So… what’s killing performance?

👉 CPU. 

🧠 CPU vs IO (Simple but Critical)

  • IO-bound → waiting on disk (reads, writes)
  • CPU-bound → heavy computations

Most people only look at IO. That’s a mistake.

❗ If IO is low and the query is still slow… CPU is your suspect.

🔥 Case #1 – Functions on Columns (The Silent Killer)


SELECT *
FROM Orders
WHERE YEAR(OrderDate) = 2025;

❌ Problem:

  • Function applied on column
  • Index NOT used
  • Full scan + CPU spike

✔️ Fix:


WHERE OrderDate >= '2025-01-01'
AND OrderDate < '2026-01-01'

💣 Functions on columns don’t just break indexes… they burn CPU.

🔥 Case #2 – Scalar UDF (The Invisible Killer)


SELECT dbo.CalculateDiscount(Amount)
FROM Orders;

❌ Problem:

  • Executed once per row
  • Breaks parallelism (in many cases)
  • Row-by-row execution

💣 Scalar functions turn set-based SQL into row-by-row execution.

🔥 Case #3 – Sorting & Hashing


SELECT *
FROM Orders
ORDER BY Amount;

👉 Without an index:

  • SORT operator
  • High CPU usage

Same for:

  • HASH JOIN
  • HASH AGGREGATE

👉 These operators are CPU hungry by design.

🔥 Case #4 – Bad Cardinality = CPU Waste

If SQL Server estimates wrong:

  • Chooses HASH instead of NESTED LOOP
  • Or the opposite

👉 Result: unnecessary CPU consumption.

🧪 Benchmark Proof (This Is Gold)


SET STATISTICS TIME ON;
SET STATISTICS IO ON;
Query CPU Time Logical Reads
With function 1500 ms 🠉 5000 (=)
Optimized 200 ms   🠟 5000 (=)

👉 Same IO.
👉 CPU drops dramatically.

🚀 How to Find CPU Killers ... Try ourself!


SELECT TOP 10
    qs.total_worker_time / qs.execution_count AS avg_cpu,
    qs.execution_count,
    st.text
FROM sys.dm_exec_query_stats qs
CROSS APPLY sys.dm_exec_sql_text(qs.sql_handle) st
ORDER BY avg_cpu DESC;

👉 This shows your worst CPU offenders.

💣 High CPU queries are invisible if you only look at IO.

💣 Final Thought

Your query is not slow… it’s expensive.

Disk can be cached, instead CPU cannot!

👉 When CPU saturates… the entire server suffers.

👉 If you want performance… start looking beyond IO.



Comments and suggestions are welcome!

Luca Biondi @2026! 




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