How to Use SQL Plan Management (SPM) - Plan Stability Worked Example (Doc ID 456518.1)

Last updated on SEPTEMBER 11, 2024

Applies to:

Goal

SQL Plan management (SPM) is a preventative mechanism that records and evaluates the execution plans of SQL statements over time. SPM builds SQL plan baselines composed of a set of existing plans that are known to be efficient. The SQL plan baselines are then used to preserve performance of corresponding SQL statements, regardless of changes occurring in the system, providing "plan stability".

Common usage scenarios where SQL plan management can improve or preserve SQL performance include:

• Database Upgrade
  A database upgrade that installs a new optimizer version usually results in plan changes for a small percentage of SQL statements, with most of the plan changes resulting in either no performance change or improvement. However, certain plan changes may cause performance regressions. The use of SQL plan baselines significantly minimizes potential performance regressions resulting from a database upgrade.
  
  
• System/Data Changes
  Ongoing system and data changes can impact plans for some SQL statements, potentially causing performance regressions. The use of SQL plan baselines will help to minimize performance regressions and stabilize SQL performance.
  
  
• Application upgrade
  Deployment of new application modules means introducing new SQL statements into the system. Application software may use appropriate SQL execution plans developed under a standard test configuration for the new SQL statements. If your system configuration is significantly different from the test configuration, the SQL plan baselines can be evolved over time to produce better performance. 

If you have a good plan in the cursor cache, then you can load these into SPM so that you can use this baseline to preserve the performance. The following example command illustrates this:

Solution