RE: Execution Plan turned "Bad"

SSC Enthusiast

Points: 152

December 15, 2017 at 3:25 pm

#1972355

Jeff Moden - Friday, December 15, 2017 10:07 AM
Even though stats are updated "every week", it could still be a stats problem. It could also be that the data finally reached a "tipping point" and caused code that doesn't necessarily scale well (despite previous "good performance") to choose a less than optimal plan.

Hi, I agree, this is the most probable scenario. But I'm confused about the plan properties (Estimated Number of Rows: 1 / Reason for Early Termination of Statement Optimization: Good Enough Plan Found) as being symptoms or cause...