Highlighting Red for Clustered Index Seek

SQLHarry 2014-04-20 15:56:59

Aaron Bertrand 2014-04-21 17:55:41
Not sure I follow – the attached plan has some clustered index seeks, but they're not the most expensive operators involved. Are you asking why they're not highlighted in red, or something else?
SQLHarry 2014-04-21 18:18:51

Question 1. Would like to hear suggestions/thoughts about improving this query.

Question 2. Clustered Index Seeks are being highlighted in Orange and Red…which means that they asking for some attention. When looked into the Data Flow actual vs Estimated are Skewed even though Stats are up-todate. How to start troubleshooting this..??

Aaron Bertrand 2014-04-21 18:27:40
Unfortunately, the query text has been stripped away, so all I have to go on are the most expensive operators. Also, there is always going to be something in your plan that is the most expensive thing. Is it actually a problem? What is the duration of this query? Did you expect it to return 0 rows?

Cardinality can be off for a variety of reasons, in addition to statistics – constantly changing data, different parameter values (I don't see those explicitly here, but I don't know how the SQL is being constructed), the use of functions and table variables, etc. Joe Sack covers a pretty thorough list here: https://www.sqlperformance.com/2012/11/t-sql-queries/ten-common-threats-to-execution-plan-quality