SQL Server: Indexes Are NOT Your First Optimization Tool (Here’s What Is) 🔥

SQL Server: Indexes Are NOT Your First Optimization Tool (Here’s What Is) 🔥

👉 If you missed my previous post: Why Your Index Is NOT Being Used (5 Hidden Reasons)

💥 The Hook

You add an index… and the query is still slow.
Or worse — everything else becomes slower.

👉 What if indexes are NOT your real problem?

TL;DR

💣 Problem → Query is slow despite indexes
💣 Symptom → High CPU, scans, unstable performance
✔️ Fix → Query rewrite + SARGability + Data model first (NOT indexes)

Hi SQL Server Guys,

Your query is slow.
So you add an index.

Sometimes it works.
Most of the time… it doesn’t.

💣 Because indexes are NOT the first optimization tool.

🧠 What It Really Is

SQL Server performance is NOT about adding indexes.

👉 It’s about how the engine can understand and execute your query efficiently.

  • Query shape matters
  • Predicate structure matters
  • Data model matters

💣 If these are wrong… indexes won’t save you.

🔥 1. Query Rewrite (The Hidden Power)

Same logic. Completely different performance. 

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

-- GOOD
SELECT *
FROM Orders
WHERE OrderDate >= '2025-01-01'
AND OrderDate < '2026-01-01';

✔️ The second query allows index usage
💣 The first forces a scan + CPU burn

🔥 2. SARGability (The Real Game)

SARGable = Search ARGument ABLE.

👉 SQL Server can use indexes ONLY if predicates are SARGable.

  • Functions on columns ❌
  • Implicit conversions ❌
  • Expressions on columns ❌

💣 Non-SARGable query = full scan = high CPU

🔥 3. Data Model (The ROOT Cause)

Bad schema = permanent performance problems.

  • Wrong datatypes
  • Over-normalization
  • Missing relationships

👉 No index can fix a bad data model.

💣 You are optimizing symptoms… not the cause.

🧪 Benchmark

Scenario CPU Reads Result
Bad Query + Index 1800 ms 500000 Slow ❌
Rewritten Query (No Index) 200 ms 5000 Fast ✔️
Rewritten + Index 50 ms 500 Optimal 🚀

💣 Index alone ≠ performance

🔥 Real Fixes

  1. Rewrite Queries
    ✔️ Huge impact
    ❌ Requires understanding
  2. Fix SARGability
    ✔️ Enables indexes
    ❌ Easy to miss
  3. Fix Data Model
    ✔️ Long-term solution
    ❌ Expensive to change
  4. Add Indexes LAST
    ✔️ Final optimization layer
    ❌ Often misused

🚀 My REAL Strategy

After 25 years tuning SQL Server:

  • 1️⃣ Fix the query FIRST
  • 2️⃣ Make it SARGable
  • 3️⃣ Validate execution plan
  • 4️⃣ Fix data model if needed
  • 5️⃣ ONLY THEN add indexes

💣 If you start with indexes… you are already wrong.

🔗 Deep Dives

📚 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