Donnie Carvajal (8/1/2013)
I checked the execution plan on the production server as well and I am seeing close to the same values for this query.The full database statistics updates have finished and I am still seeing estimated rows at 206975. Any other suggestions? See attached for latest plan.
Donnie
"Un-nest" your views. Nested views are generally horrible for performance. I suspect this is what you are running into. Try putting together the same query by un-nesting your views and see what the plan looks like at that point.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/