wrong estimation at Hash Match

In an inner join on a table with up-to-date full scan statistics the hash match estimated 2.760 rows (149K) , whereas the actuals are 544.700.285. This leads to a spill in the tempDB in a sort later on. How to investigate where this mismatch comes from and how to correct this? alt text

e-vs-a.jpg (24.6 kB)
avatar image By SirWilliam 1 asked Jul 14, 2017 at 09:29 AM
more ▼
(comments are locked)
avatar image Matak Jul 16, 2017 at 10:59 PM

Pictures of execution plans dont help at all. Can you attach the actual plan ?

10|10000 characters needed characters left

0 answers: sort voted first
Be the first one to answer this question
toggle preview:

Up to 50 attachments (including images) can be used with a maximum of 209.7 MB each and 209.7 MB total.

We are Moving!


Follow this question



asked: Jul 14, 2017 at 09:29 AM

Seen: 461 times

Last Updated: Jul 16, 2017 at 10:59 PM