In Part 1 of this series of tips on SQL Plan Management (SPM) and Oracle Database In-Memory I covered an example where a full table scan query made use of the In-Memory column store immediately without changing the SQL execution plan. In Part 2 I presented an example where the In-Memory column store made an alternative SQL execution plan viable, and where there was a corresponding SQL plan baseline already in place so that this plan could be used immediately.
In this post I will consider a slightly different scenario:
- SQL plan management is used to stabilize the SQL execution plans for our critical application (that until now has not been using the In-Memory column store).
- The In-Memory column store is subsequently enabled and populated with application tables.
- The Optimizer identifies new SQL execution plans.
- Most of the new execution plans have never been chosen by the Optimizer before.
Continuar aqui
No hay comentarios:
Publicar un comentario