Physical Join Operators in SQL Server - Merge Operator
Part II of the Physical Joins series looks at the Merge operator.
2010-07-05
4,112 reads
Part II of the Physical Joins series looks at the Merge operator.
2010-07-05
4,112 reads
Continuing to illuminate the depths of SQL Server's Query Optimizer, Fabiano shines a light on the sixth major Showplan Operator on his list: the Lazy Spool. What does the Lazy Spool do that's so special, how does the Query Optimizer use it, and why is it so Lazy? Fabiano Amorim explains all.
2010-06-28
2,774 reads
The Query Optimizer gets it right most of the time, but occasionally it chooses a plan that isn't the best possible. You can give the Query Optimiser a better idea by using Table, Join and Query hints. These come with a risk: Any choices you force on the Optimizer by using hints can turn out to be entirely wrong as the database changes with the addition of data over time. Grant Fritchey, in a chapter from his highly acclaimed book, explains further.
2009-11-25
3,275 reads
2009-04-24
3,399 reads
Keeping in mind the importance of the cache mechanism, how could one get the plans and their usage statistics in SQL Server?
2009-01-19
4,183 reads
Learning how to read and analyze execution plans takes time and effort. But once you gain some experience, you will find them an essential skill for getting to grips with performance issues in SQL Server Queries. Grant here describes the range of execution plans for different simple SQL Queries.
2009-01-05
5,326 reads
By Steve Jones
I had a conversation with a customer asking this question: how can I tell...
By Chris Yates
There was a time when the Chief Data Officer lived in the shadows of...
By Rayis Imayev
"But I don’t want to go among mad people," Alice remarked."Oh, you can’t help...
Comments posted to this topic are about the item Create an HTML Report on...
Hi everyone I am getting an error when I create the index but I...
Good morning all, I have been running into a very random weird issue that...
I have two calls to the GENERATE_SERIES TVF in this code:
SELECT TOP 10 gs.value FROM GENERATE_SERIES(1, 10) AS gs ORDER BY NEWID () OPTION (RECOMPILE); go DECLARE @a int = 10; SELECT TOP (@a) gs.value FROM GENERATE_SERIES(1, @a) AS gs ORDER BY NEWID () OPTION (RECOMPILE);In the actual query plans, what is the estimated number of rows for each batch in SQL Server 2022? See possible answers