table scan operator

sakuraime 2,351 Reputation points
2021-08-23T09:45:42.56+00:00

From the execution plan , I have got a operator call table scan .

it has

estimated number of executions : 1.0.....
estimated number of rows to be read: 45899 < which is the rows of the table
estimated number of rows for all execution : 58.
Estimated number of rows per executions: 57

so why estimated number of rows for all execution is not 45899 ?

125603-image.png

what means the table scan to be stopped at the row of 58 ?

SQL Server | Other
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Erland Sommarskog 129.4K Reputation points MVP Volunteer Moderator
    2021-08-23T21:08:03.327+00:00

    It would have helped to see the full popup, but I guess that there is a predicate that filters out rows.

    0 comments No comments

  2. CathyJi-MSFT 22,406 Reputation points Microsoft External Staff
    2021-08-24T03:09:58.96+00:00

    Hi @sakuraime ,

    Estimated Number of Rows to be Read

    This is an estimate of the number of rows that will be read by the operator as it is scanning the heap. The difference between this property and the Estimated Number of Rows or Estimated Number of Rows Per Execution property represents the number of rows that is estimated to be read but not returned due to the Predicate property.

    Estimated Number of Rows for All Executions

    An estimation of how many rows the operator will return for all (estimated) executions combined.
    This property is not actually included in the execution plan. Tools such as Management Studio (version 18.5 and higher) computed it by multiplying the Estimated Number of Rows to the Estimated Number of Executions.

    Refer to the blog Table Scan.


    If the response is helpful, please click "Accept Answer" and upvote it, as this could help other community members looking for similar thread.


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.