Physical Join Operators in SQL Server - Hash Operator
In the concluding part of the Physical Operators series we look at the Hash operator.
2010-07-12
3,790 reads
In the concluding part of the Physical Operators series we look at the Hash operator.
2010-07-12
3,790 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,410 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
This month’s blogging party is hosted by Jeff Ianucci – his challenge is to...
As for me, I'll keep writing whenever time permits. I don't expect every post...
By Steve Jones
This is an interesting invitation this month. Jeff Ianucci is a new host, and...
Comments posted to this topic are about the item Pay for Performance, which is...
Comments posted to this topic are about the item Switching Schemas I
Comments posted to this topic are about the item Enforcing Unique Customer Emails When...
I run this query:
SELECT s.name AS schemaname , o.name AS objectname FROM sys.objects o INNER JOIN sys.schemas s ON s.schema_id = o.schema_id WHERE o.name = 'Beer'I get one row back for an object named dbo.beer. There is an ETL schema and both of these are nonpartitioned tables. I run this code:
ALTER TABLE dbo.beer switch TO etl.beerWhat happens? See possible answers