Hugo Kornelis provides one example of misleading arrow widths in execution plans:
In my previous post, I talked about the Actual Number of Rows and Estimated Number of Rows properties, their visual representation in execution plans, and the most important ways in which this can be used.
But life is not always perfect, and Microsoft likes to remind us of that. Sometimes, these properties report values in weird and confusing ways. Sometimes the arrow width, as the visual representation in the execution plan, misleads us.
Let’s look at one such case.
Read the whole thing and vote for Hugo’s Feedback item to improve this experience.