Do you have a comment or suggestion to improve SQL Server? We’d love to hear it!

Incorrect arrow width in execution plans (SSMS 17.4)

When showing execution plans in SSMS 17.4, the arrow width is incorrectly based on the ""Number of Rows Read"property (for operaotrs that report it), instead of Äctual Number of Rows". This makes execution plans confusing and misleading when the plan uses scans with pushed-down predicates.

Example:
SELECT * FROM Person.Person AS p
WHERE p.Title = 'xx'
ORDER BY p.EmailPromotion;

On SSMS 17.4, the execution plan shows a thick arrow going into the sort and a thin arrow going out of it. The thick arrow is based on the 19972 rows read withing the clustered index scan operator, but since none of them satisfy the where clause zero rows were actually passed to the sort operator.

16 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Hugo Kornelis shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    declined  ·  AdminMicrosoft SQL Server (Admin, Microsoft Azure) responded  · 

    Hello Hugo, the thickness now takes into account the actual rows read by the operator, if available, which as per previous user community feedback, is a more accurate measure of the operator weight in the plan, and it makes it easier to pinpoint problem areas. In some cases, the problem operator had the narrowest line as actual rows is zero, but actual rows read was > 0.

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base