"Join Types and What They Tell You"

1. What does an INNER JOIN operation expecting a Nested Loops join indicate about the optimizer's estimate?

The optimizer expected a large outer input The optimizer expected a small outer input The optimizer expected large inner and small outer inputs The optimizer has no expectations

2. When is a Hash Match join considered beneficial according to the lesson?

When joining small sets When joining big sets When there is an explicit Sort operation When there are no indexes available

3. What does a Merge Join with a preceding Sort operator likely indicate?

The Sort operation is cheaper than the Join The inputs are already sorted The Sort may cost more than the Join saves The optimizer expected a Nested Loops join

4. Which join type indicates that the optimizer believed the input data was small and may need investigation?

Hash Match Nested Loops Merge Join Cross Join

Continue: "Warnings, Spills, and Memory Grants" → Review this lesson Retake quiz