Nested Loop vs Hash Join vs Merge Join – The Truth Nobody Explains



🔥 Nested Loop vs Hash Join vs Merge Join – The Truth Nobody Explains

Hi SQL Server Guys,

Welcome to this news post! Today on the menu we have the JOIN OPERATORS. Ready to learn important things?

👉 If you missed my previous posts, check these first:
Execution Plans – Read in 10 Minutes | CPU vs IO – Hidden Bottlenecks

1️⃣ Understanding the Join Operators

SQL Server has three main join operators you’ll encounter in execution plans: Nested Loop, Hash Join, and Merge Join. Each has strengths, weaknesses, and hidden trade-offs between CPU and IO.

Things to know about:

Nested Loop Join

- Reads one row from the outer table and searches matching rows in the inner table.
- Ideal for small datasets or when the inner table is indexed.
- CPU light for small datasets but IO cost grows linearly as dataset size increases.

Hash Join

- Builds a hash table on the smaller input and probes it with the larger table.
- Excellent for large, unindexed tables.
- CPU heavy (hashing), low IO cost, predictable for big datasets.

Merge Join

- Requires both inputs to be sorted on join keys.
- Extremely efficient for pre-sorted/indexed tables.
- CPU light, minimal IO, but can fail if sorting is needed on large tables.

2️⃣ How SQL Server Chooses the Join

Typically:

  • Nested Loop → small datasets, efficient when the inner table is indexed
  • Hash Join → large datasets, especially when data is not sorted or indexed
  • Merge Join → best when both inputs are already sorted (or can be efficiently sorted)

👉 Behind the scenes, SQL Server uses statistics, cardinality estimates, and a cost-based model to select the operator with the lowest estimated cost.

P.S. Keep in mind this concept: SQL Server does not evaluate every possible execution plan. Instead, it explores only a subset of plans using heuristics and cost-based optimization. When it finds a plan that is “good enough”, it stops searching and executes it.

👉 This means SQL Server does not always choose the best possible plan instead it chooses the best plan it can find within the available search space and optimization time.

And this explains why you sometimes see:

  • Unstable query performance
  • Parameter sniffing issues
  • “Weird” or unexpected execution plans

3️⃣ Common Mistakes & Pitfalls

  • Ignoring row estimates → can force Nested Loops on huge datasets.
  • Assuming Hash Join is always CPU-heavy → depends on memory availability.
  • Relying on Merge Join → sorting can dominate IO cost if indexes are missing.
  • Over-indexing → can mislead the optimizer into picking the “wrong” join.

4️⃣ Real Benchmarks – Nested Loop vs Hash vs Merge

Join Type Rows Processed CPU (ms) IO (MB) Notes
Nested Loop 1,000,000 120 450 Fast for small inner table, linear growth for outer
Hash Join 1,000,000 300 150 CPU heavy, low IO, best for large unsorted tables
Merge Join 1,000,000 100 120 Fastest if tables sorted, minimal CPU/IO

5️⃣ Key Takeaways

  • One join operator does not fit all scenarios.
  • Know your row counts, indexes, and data distribution.
  • CPU vs IO trade-off is the secret sauce of SQL Server performance.
  • Always check the execution plan before guessing.

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