Tchater maintenant avec le support
Tchattez avec un ingénieur du support

SQL Optimizer for Oracle 10.0 - User Guide

Welcome to SQL Optimizer
About SQL Optimizer SQL Optimization Workflow New in This Release Additional Resources Database Privileges Database Privileges Script Connect to the Database Windows Layout Customize Toolbars Keyboard Shortcuts Support Bundle Register SQL Optimizer Check for Updates SQL Operations
ALL PARTITION ALTER INDEX AND EQUAL ANTI JOIN BITMAP AND BITMAP COMPACTION BITMAP CONSTRUCTION BITMAP CONVERSION BITMAP INDEX BITMAP JOIN INDEX UPDATE BITMAP JOIN INDEX UPDATE STATEMENT BITMAP KEY ITERATION BITMAP MERGE BITMAP MINUS BITMAP OR BUFFER SORT CARTESIAN JOIN COLLECTION ITERATOR CONCATENATION CONNECT BY CONNECT BY PUMP COUNT COUNT STOPKEY CREATE AS SELECT CUBE SCAN DDL STATEMENT DELETE DOMAIN INDEX FAST FULL INDEX SCAN FILTER FIRST ROWS FIXED INDEX FIXED TABLE FOR UPDATE FULL INDEX SCAN FULL INDEX SCAN DESCENDING FULL INDEX SCAN (MIN/MAX) HASH GROUP BY HASH GROUP BY PIVOT HASH JOIN HASH JOIN BUFFERED HASH PARTITION HASH UNIQUE INDEX INDEX BUILD NON UNIQUE INDEX RANGE SCAN INDEX RANGE SCAN DESCENDING INDEX RANGE SCAN (MIN/MAX) INDEX SAMPLE FAST FULL SCAN INDEX SKIP SCAN INDEX SKIP SCAN DESCENDING INDEX UNIQUE SCAN INLIST ITERATOR INLIST PARTITION INSERT INTERSECTION INTO INVALID PARTITION ITERATOR PARTITION LOAD AS SELECT MAT_VIEW ACCESS MAT_VIEW REWRITE ACCESS MERGE JOIN MINUS MULTI-TABLE INSERT NESTED LOOPS OUTER JOIN PARTITION PARTITION HASH EMPTY PARTITION LIST PARTITION RANGE PROJECTION PX BLOCK ITERATOR PX COORDINATOR PX ITERATOR PX PARTITION PX PARTITION HASH ALL PX PARTITION LIST ALL PX PARTITION RANGE ALL PX RECEIVE PX SEND RANGE PARTITION RECURSIVE EXECUTION RECURSIVE WITH PUMP REFERENCE MODEL REMOTE SELECT SEMI JOIN SEQUENCE SINGLE PARTITION SINGLE RANGE PARTITION SORT SORT AGGREGATE SORT GROUP BY SORT GROUP BY CUBE SORT GROUP BY NOSORT SORT GROUP BY ROLLUP SORT JOIN SORT ORDER BY SORT UNIQUE SQL MODEL TABLE ACCESS TABLE ACCESS BY GLOBAL INDEX ROWID TABLE ACCESS BY INDEX ROWID TABLE ACCESS BY LOCAL INDEX ROWID TABLE ACCESS BY ROWID TABLE ACCESS BY USER ROWID TABLE ACCESS CLUSTER TABLE ACCESS FULL TABLE ACCESS HASH TABLE ACCESS SAMPLE TABLE QUEUE TEMP TABLE GENERATION TEMP TABLE TRANSFORMATION UNION UNION ALL UNION ALL (RECURSIVE WITH) UNPIVOT UPDATE VIEW VIEW PUSHED PREDICATE WINDOW
Optimize SQL
Create Optimize SQL Sessions Open Optimizer SQL Sessions Rewrite SQL Generate Execution Plan Alternatives
Optimize Indexes Batch Optimize SQL Scan SQL Inspect SGA Analyze Impact Manage Plans Configure Options SQL Optimizer Tutorials About Us Legal Notices

Test for Scalability (Optimize SQL)

When you optimize a SQL statement, it is important to consider the scalability of the alternatives SQL Optimizer generates before you implement them in your production database. SQL performance and scalability are two important factors that determine a database application's ability to handle an increase user load. The performance of a SQL statement changes as the number of users increase. Performance problems can arise when you use certain SQL statements under a heavy user load.

Note: This topic focuses on information that may be unfamiliar to you. It does not include all step and field descriptions.

To test for scalability

  1. Select the Optimize SQL tab in the main window.
  2. Select a SQL Rewrite session.

  3. Select a SQL statement in the Alternatives pane.

  4. Click the arrow beside and select an option.

  5. Review the following for additional information:

    Minimum number of virtual users

    Enter the minimum number of virtual users to use for scalability testing.

    Range: 1 to 1,000,000,000

    Maximum number of virtual users

    Enter the maximum number of virtual users to use for scalability testing.

    Range: 1 to 1,000,000,000

    Step value of virtual users

    Enter the number of virtual users to increase by for each step of scalability testing.

    Range: 1 to 1,000,000,000

    Distribution Model

    Select a latency think time distribution model:

    • None—Does not insert a latency think time between executions.
    • Absolute—Uses the value entered in the Duration field as the latency think time between executions.
    • Uniform—Uses a random duration between 1 millisecond and the value entered in the Duration field as the latency think time.
    • Negative Exponential—Uses a random duration based on a mathematical model weighted towards lower latency think times. The value entered in the Duration field is used for calculating think times.
    • Normal—Uses a random duration based on a mathematical model weighted towards average latency think times. The value entered in the Duration field is used for calculating think times.
    • Poisson—Uses a random duration based on a mathematical model weighted towards discrete latency think times. The value entered in the Duration field is used for calculating think times.
    Duration (milliseconds)

    Enter a duration in milliseconds.

    Note: How SQL Optimizer uses the value you enter depends on the distribution model selected.

    Execute Each SQL Statement by

    Select one of the following:

    • Duration (seconds)—Enter the duration of the scalability test in seconds.

    • Number of times—Enter the number of times to execute the SQL statement.

      Range: 1 to 100

  

Related Topics

About Optimizing SQL (SQL Rewrite)

Automatically Optimize SQL Statements

Alter Session Parameters

This topic focuses on information that may be unfamiliar to you. It does not include all step and field descriptions.

To alter session parameters

  1. Right-click the Alternative Details or SQL Text pane and select Alter Session Parameters.

    Tip: You can also alter session parameters for alternatives by right-clicking the alternative in the Alternatives or Plans pane and selecting Alter Session Parameters.

  2. Enter or select a new Oracle session parameter.

Notes:

  • You must alter session parameters for SQL statements or alternatives individually.

  • To alter session parameters, you must have access to the SYS.V_$PARAMETER system view.

 

Retrieve Run Results

In an Optimize SQL session (SQL Rewrite or Plan Control), you can execute the original or an alternative SQL statement to retrieve and review the statement's result set.

To retrieve result set

  1. Right-click the selected statement in the Alternatives list (or right-click the SQL text) and select Run Result.

  2. In the Run Result dialog, click . After the script executes, the result set displays in the Result pane of the Run Result dialog.

    Tip: Click to copy the SQL statement to execute in another Quest Software product.

 

 

Review Alternatives

This topic focuses on information that may be unfamiliar to you. It does not include all step and field descriptions.

To review details for an alternative

  1. Select the Optimize SQL tab in the main window.
  2. Select a SQL Rewrite session.

  3. Select a SQL statement or index alternative in the Alternatives pane.

  4. Review the details of the alternative in the Execution Plan pane.

    Note: You must execute the alternatives before you can review run time statistics.

  

Related Topics  

About Optimizing SQL (SQL Rewrite)

 

 

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation