Hello !
I'm looking at the query Excecution plan, there is CLUSTERED INDEX SEEK
operation and the numbers are:

ROW COUNT: 6 850 703
Estimated Row Count:  554

But in fact there is only  2 557 244 rows in the table.

How to explain and repair ?


Kuido

Did you update statistics?


AMB

Show quoteHide quote

Since you see both "row count" and "estimated row count", you must
be looking at an actual execution plan, not an estimated execution plan.
The estimated and actual row counts are expressed differently.  In
the estimated plan (and shown in the actual plan), you have

  Estimated row count [this is "per execution"]
  Number of executes

In the actual plan, there is just one row count

  Row count [this is the total for all executions]

If the clustered index seek is executed more than once, the
row count can easily exceed the number of rows in the table,
since it is executed more than once.

Steve Kass
Drew University

Kuido Külm via SQLMonster.com wrote:

Show quoteHide quote

Can I do this?
is there a set-based solution to this task?
Basic Query Help
Fetch statement
DTS Issue while calling from another domain