When Plan Changes are Bad

A plan change is only a problem when the new plan is worse. Symptoms include:

• Increased runtime
• Increased temp usage (due to spills)
• Higher CPU or I/O
• Lower row estimates than actuals
• Drastically different join orders