Does the difference between the estimated and actual rows seem ok?

I am a looking at an nonclustered index node on my excution plan.

The estimated amount of rows = 15.
The actual amount of rows = 409.

My statistics were updated last night at 11:44.

Does the difference between the estimated and actual seem ok?
Mr_ShawAsked:
Who is Participating?
 
Raja Jegan RSQL Server DBA & ArchitectCommented:
Yes, it happens most of the times..
But its not desirable from our perspective and it shows the chances of improving or optimizing our query.
Even though our tables have appropriate indexes created, there might be chances that

1. Indexes are not properly utilized for execution of the query.
2. Statistics generated is not being used by the Query Optimizer

And the possible solutions that can be implemented are listed in this article clearly:
http://www.simple-talk.com/sql/performance/sql-server-statistics-problems-and-solutions/
0
 
Aaron ShiloChief Database ArchitectCommented:
LET ME ADD ONE MORE THING

the optimizer calculates the CARDINALITY and isent allways aqurate.

read more : http://msdn.microsoft.com/en-us/library/ms181034.aspx
0
 
qasim_mdCommented:
Yes this is fine. Estimated is the no of rows that will be read with your query and Actual is the total number of rows in the table
0
 
Anthony PerkinsCommented:
>>Estimated is the no of rows that will be read with your query and Actual is the total number of rows in the table <<
You may want to double check that.
0
 
Mr_ShawAuthor Commented:
thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.