Why a procedure with abstract plan attached got a different plan atexecution time??? - 08-19-2011 , 03:36 PM
We recently upgraded to Sybase 15.0.3, and have seen radom bad query
plans since upgrade.
We added plan " " clause to one stored procedure, but still got a
different plan at execution time with totally different join orders.
It does not happy all the time, 99.9% of the time the plan is the
forced one, but that 0.1% time it took the wrong plan, the proc would
run for over a hour and had to be killed.
I'd appreciate advice or anyone sharing similar experience.