Why is the estimated number of rows in this query so much higherf than the actual returned rows? Any help or suggestions apprceiated.
Up to 50 attachments (including images) can be used with a maximum of 209.7 MB each and 209.7 MB total.
Answers and Comments
query plan x673
plan explorer upload x484
execution plan x123
index tunning x39
asked: Sep 11, 2017 at 12:29 PM
Seen: 45 times
Last Updated: Sep 11, 2017 at 12:29 PM
Component running slow
Bad Estimated I/O Cost
Concered with the Est Rows vs Actual Row Count
Avoiding hash Match by using covering index on object2.index2
How can I get rid of the bad cardinality in this plan
The SP is timing out after addition of 2 new filters of state and City
Top N Sort issue
would like to tune the query
Can index Scan be replaced with index seek, in order to avoid a huge scan
to get rid of key lookups, do I add all the where clause columns to covered index or just create a new index on its own. Which one is better or best practised then the others
© 2013 SQL Sentry, Inc. All rights reserved.