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