Execution plan change
Hi All,
We have few jobs which runs on daily basis. From last few days we are having some problem with some of the jobs behavior.
Job contains sql statements which refreshes data from multiple tables to one table. It runs fine for 3-4 days and suddenly on 5th day it's picking the different plan which is running hours together to complete and the execution time with previous run is uncomparable.
My question here is why this sql statement suddenly changing the execution plan for which even cost looks double compared with other previous plan. It uses bind variables in where clause and all the tables stats are up-to-date. And because of this i can see only CPU waits for very time.
We have few jobs which runs on daily basis. From last few days we are having some problem with some of the jobs behavior.
Job contains sql statements which refreshes data from multiple tables to one table. It runs fine for 3-4 days and suddenly on 5th day it's picking the different plan which is running hours together to complete and the execution time with previous run is uncomparable.
My question here is why this sql statement suddenly changing the execution plan for which even cost looks double compared with other previous plan. It uses bind variables in where clause and all the tables stats are up-to-date. And because of this i can see only CPU waits for very time.
0