I am not sure why the Index Seek returning 9,788 rows becomes 127,929.160 in the Lzay Table Spool.
By RobertOD 16 asked Oct 13, 2014 at 11:14 PM
The section of the plan in question is:
The 9,788 rows read from the Index Seek are replayed by the spool once for each row arriving at the Nested Loops join's top input. **9788 13,070 = 127,929,160*.
The Nested Loops join applies the following predicate on each replay:
A better strategy would be to perform a correlated seek, with no join residual. You should check the indexes available on the table underlying this view to make sure the correlated seek strategy is viable.
By SQLkiwi ♦ 6.6k answered Oct 14, 2014 at 09:14 AM