SQL SERVER, Parameter Sniffing: The Bug That Isn’t a Bug (But Breaks Everything)

SQL Server Parameter Sniffing: The Bug That Isn’t a Bug (But Breaks Everything) 🔥

👉 If you missed my previous post:
How to Find the Slowest Queries in SQL Server in 60 Seconds 💪


In this post, you will learn how to identify and defeat erratic performance in SQL Server. If your queries go from "lightning-fast" to "crawling" without warning, you are a victim of Parameter Sniffing. It’s time to regain control of your Execution Plans and stop the unpredictability.


Hi SQL Server Guys,

Your query is fast, then suddenly… it becomes slow!
You have: 

  • Same query.
  • Same data.
  • Same server.

👉 What changed?

💣 Parameter Sniffing

And no… it’s NOT a bug.

👉 It’s how SQL Server is designed to work.

🧠 What Parameter Sniffing Really Is

When SQL Server compiles a query or stored procedure, it uses the first parameter value to generate an execution plan.

👉 That value is “sniffed” and used for optimization.

The problem?

👉 That plan is reused… even when parameters change.

💣 We have one plan for multiple realities.

🔥 When It Happens

It happens for:
  • Stored procedures
  • Parameterized queries
  • Highly skewed data distributions
  • Different selectivity values

👉 Example: 

SELECT *
FROM Orders
WHERE CustomerID = @CustomerID;

If he have for example skewed data where:

  • Customer A has only 1 row
  • Customer B has 1,000,000 rows

💣 The same query should have completely different optimal plans.

⚔️ The Real Problem

SQL Server picks ONE plan based on the first execution.

👉 And reuses it blindly.

💣 This is why queries become unstable.

  • Fast sometimes
  • Slow other times
  • Impossible to predict

🧪 Benchmark (Real Scenario)

SET STATISTICS TIME ON;
SET STATISTICS IO ON;

-- First execution (small dataset)
EXEC GetOrders @CustomerID = 1;

-- Second execution (large dataset)
EXEC GetOrders @CustomerID = 9999;
Scenario CPU Reads Plan
Small → Plan Cached 50 ms 200 Index Seek
Large → Reused Plan 2000 ms 500000 Index Seek ❌

💣 Same plan. Wrong choice.

🔥 Real Fixes

1️⃣ OPTION (RECOMPILE)

SELECT *
FROM Orders
WHERE CustomerID = @CustomerID
OPTION (RECOMPILE);

✔️ Always optimal plan
❌ CPU overhead (recompilation)

2️⃣ OPTIMIZE FOR

OPTION (OPTIMIZE FOR (@CustomerID = 1));

✔️ Stable plan
❌ Not adaptive

3️⃣ OPTIMIZE FOR UNKNOWN

OPTION (OPTIMIZE FOR UNKNOWN);

✔️ Uses average distribution
✔️ Safer for mixed workloads

🚀 My REAL Strategy (Most Important Part)

My TIPS! 

Stop thinking in terms of “fix” , think instead in terms of workload patterns.

  • Few executions → RECOMPILE
  • Predictable workload → OPTIMIZE FOR
  • Mixed workload → UNKNOWN
  • Critical queries → custom logic / dynamic SQL

💣 Keep in mind that there is NO universal solution.

👉 ...Only trade-offs.

🔗 You could be interested also in...

💣 Final Thought

“Parameter sniffing is not a bug…
it’s an optimization strategy.”

👉 But in the wrong scenario…

…it becomes your worst nightmare.

📚 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 👀, feel free to take a look! Your engagement helps me continue publishing premium SQL Server content for the community.


Biondi Luca @2026 - Sharing my over 25 years of Gained Knowlegde for Passion.
share if you like my posts and found them useful

Comments

Post a Comment

I Post più popolari

SQL Server, Sub-Queries vs. Cross Apply

Image
Hi Guys, Today for you a basic post! We do a comparison between a Query with Sub-Queries and with the Apply operator! So, what are differences between using sub-query and using cross/Outer Apply? Well, if you don't know you should absolutely read this post! Introduction For our comparison we choose these queries:     A query with two sub-queries (A subquery is simply a query with another query inside it's select) Select ( Select MAX (OrdRig.Qta1) as conta from OrdRig where Ordrig.idordtes = o.Id and OrdRig.IdComrig is not null), ( Select MAX (OrdRig.Qta2) as conta from OrdRig where Ordrig.idordtes = o.Id and OrdRig.IdComrig is not null) From eco..ordtes o   A query that use a Cross Apply operator select t . Qta1 , t . Qta2 from eco .. ordtes o CROSS APPLY   ( Select MAX ( OrdRig . Qta1 ) as Qta1 , MAX ( OrdRig . Qta2 ) as Qta2    from OrdRig    where Ordrig . ido...
Read more

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