September 27, 2013 at 1:50 am
johntam (9/26/2013)
Updating stats on all of the affected tables with FULLSCAN solved the problem.
That's what I suspected. The plans showed different estimated row counts, so that was a second indication that the problem was stats-related.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 27, 2013 at 9:59 am
Gail, In the interest of learning something new, do you know of a post which describes the accepted method for posting XML query plans?
Thanks!
September 27, 2013 at 10:08 am
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
September 27, 2013 at 10:18 am
Thank you very much, I have seen the link and sheepishly admit to reading the article but, I have never gotten to the bottom where the query plan details are.
I apologize for a time-wasting question (I don't believe in stupid questions but there are plenty of time-wasting/laziness questions.)
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply