9 Creating a Pre-Change SQL Trial

After creating a SQL Performance Analyzer task and selecting a SQL tuning set as the input source, you need to establish the initial environment on the test system. Establishing the database environment on the test system involves manually making any necessary environmental changes that affect SQL optimization and performance. These changes may include changing initialization parameters, gathering or setting optimizer statistics, and creating indexes. For information about setting up the database environment, see "Setting Up the Test System".

Once the environment on the test system is properly configured, you can build the pre-change version of performance data by executing the SQL workload before performing the system change. SQL Performance Analyzer will store the results from executing the SQL statements in a pre-change SQL trial. For more information, see "Measuring the Pre-Change SQL Performance"

This chapter described how to create the pre-change SQL trial and contains the following topics:

Creating a Pre-Change SQL Trial Using Enterprise Manager
Creating a Pre-Change SQL Trial Using APIs

Note:

The primary interface for creating a pre-change SQL trial is Oracle Enterprise Manager. If for some reason Oracle Enterprise Manager is unavailable, you can create a pre-change SQL trial using the DBMS_SQLPA PL/SQL package.

Tip:

Before creating a pre-change SQL trial, you need to create a SQL Performance Analyzer task, as described in Chapter 8, "Creating an Analysis Task".

Creating a Pre-Change SQL Trial Using Enterprise Manager

To collect the pre-change SQL performance data using Oracle Enterprise Manager:

On the Guided Workflow page, click the Execute icon for the Replay SQL Tuning Set in Initial Environment step.

The Create SQL Trial page appears. A summary of the selected SQL tuning set containing the SQL workload is displayed.

Description of the illustration spa_create_trial.gif
In the SQL Trial Name field, enter the name of the SQL trial.
In the SQL Trial Description field, enter a description of the SQL trial.
In the Creation Method list, determine how the SQL trial is created and what contents are generated by performing one of the following actions:
- Select Execute SQLs Locally.
  
  The SQL trial generates both execution plans and statistics for each SQL statement in the SQL tuning set by actually running the SQL statements locally on the test system.
- Select Execute SQLs Remotely.
  
  The SQL trial generates both execution plans and statistics for each SQL statement in the SQL tuning set by actually running the SQL statements remotely on another test system over a public database link.
- Select Generate Plans Locally.
  
  The SQL trial invokes the optimizer to create execution plans locally on the test system without actually running the SQL statements.
- Select Generate Plans Remotely.
  
  The SQL trial invokes the optimizer to create execution plans remotely on another test system over a public database link without actually running the SQL statements.
- Select Build From SQL Tuning Set.
  
  The SQL trial copies the execution plans and statistics from the SQL tuning set directly into the trial.
In the Per-SQL Time Limit list, determine the time limit for SQL execution during the trial by performing one of the following actions:
- Select Unlimited.
  
  The execution will run each SQL statement in the SQL tuning set to completion and gather performance data. Collecting execution statistics provides greater accuracy in the performance analysis but takes a longer time. Using this setting is not recommended because the task may be stalled by one SQL statement for a prolonged period of time.
- Select Customize and enter the specified number of seconds, minutes, or hours.
Ensure that the database environment on the test system matches the production environment as closely as possible, and select Trial environment established.
In the Schedule section:
1. In the Time Zone list, select your time zone code.
2. Select Immediately to start the task now, or Later to schedule the task to start at a time specified using the Date and Time fields.
Click Submit.

The Guided Workflow page appears when the execution begins.

The status icon of this step changes to a clock while the execution is in progress. To refresh the status icon, click Refresh. Depending on the options selected and the size of the SQL workload, the execution may take a long time to complete. After the execution is completed, the Status icon will change to a check mark and the Execute icon for the next step is enabled.
Once the pre-change performance data is built, you can make the system change and build the post-change performance data by re-executing the SQL statements in the SQL tuning set on the post-change test system, as described in Chapter 10, "Creating a Post-Change SQL Trial".

Creating a Pre-Change SQL Trial Using APIs

This section describes how to build the pre-change performance data by using the DBMS_SQLPA.EXECUTE_ANALYSIS_TASK procedure.

Call the EXECUTE_ANALYSIS_TASK procedure using the following parameters:

Set the task_name parameter to the name of the SQL Performance Analyzer task that you want to execute.
Set the execution_type parameter in either of the following ways:
- Set to EXPLAIN PLAN to generate execution plans for all SQL statements in the SQL tuning set without executing them.
- Set to TEST EXECUTE (recommended) to execute all statements in the SQL tuning set and generate their execution plans and statistics. When TEST EXECUTE is specified, the procedure generates execution plans and execution statistics. The execution statistics enable SQL Performance Analyzer to identify SQL statements that have improved or regressed. Collecting execution statistics in addition to generating execution plans provides greater accuracy in the performance analysis, but takes longer.
Specify a name to identify the execution using the execution_name parameter. If not specified, then SQL Performance Analyzer automatically generates a name for the task execution.
Specify execution parameters using the execution_params parameters. The execution_params parameters are specified as (name, value) pairs for the specified execution. For example, you can set the following execution parameters:
- The time_limit parameter specifies the global time limit to process all SQL statements in a SQL tuning set before timing out.
- The local_time_limit parameter specifies the time limit to process each SQL statement in a SQL tuning set before timing out.
- To perform a remote test execute, set the DATABASE_LINK task parameter to the global name of a public database link connecting to a user with the EXECUTE privilege for the DBMS_SQLPA package and the ADVISOR privilege on the test system.

The following example illustrates a function call made before a system change:

EXEC DBMS_SQLPA.EXECUTE_ANALYSIS_TASK(task_name => 'my_spa_task', -
       execution_type => 'TEST EXECUTE', - 
       execution_name => 'my_exec_BEFORE_change');

Once the pre-change performance data is built, you can make the system change and build the post-change performance data by re-executing the SQL statements in the SQL tuning set on the post-change test system, as described in Chapter 10, "Creating a Post-Change SQL Trial".