Features and Benefits

Batch Optimization – Allows you to optimize problematic SQL statements from multiple sources and provides you with the optimized code that you can implement. The Batch Optimizer does this by automating the process of identifying problematic SQL, rewriting SQL statements, locating the fastest SQL alternative and generating the optimized code for multiple SQL from multiple sources.

SQL Scanner – Identifies SQL statements from source code and database objects without requiring the execution of the SQL statements. Once the SQL statements are identified, the SQL Scanner analyzes and categorizes them according to suspected levels of performance problems.

SGA Inspector – The SGA Inspector allows you to identify resource intensive SQL statements from the Oracle’s system global area (SGA). You can capture previously executed and currently running SQL statements from the SGA. You can specify your own criteria to retrieve the SQL statements and their corresponding statistics to review SQL performance. Collections can be scheduled. 

Tuning Lab – Offers you an environment to tune a single SQL statement. The Tuning Lab contains the following main functionality: SQL Optimizer, Deploy Outline, the Index Expert, Test for Scalability and Best Practices along with the testing of the alternative SQL statements and the index candidates.

• The SQL Optimizer automates the optimization of SQL statements. It first analyzes the original SQL statement, then uses Artificial Intelligence to exhaustively rewrite the syntax and apply the Oracle optimization hints. It produces a list of semantically equivalent and syntactically correct SQL statements. You can then test run the SQL statements to identify which one best suits your database environment­.
• The Deploy Outline stores an Oracle stored outline for a specific SQL statement, which Oracle will use when executing the SQL statement, in place of using the execution plan. This is helpful when tuning SQL statements with no source code changes.       
• The Index Expert enables you to determine the best possible indexes for your SQL statements. It analyzes the syntax of a SQL statement and the relation between tables to generate virtual index alternatives. Then, it provides all of the alternative index sets that generate a unique execution plan for a SQL statement (without physically creating the indexes in your database). You can compare these index recommendations and virtual execution plans and decide whether to execute them, to create the indexes or time the SQL statement under different index scenarios. Alternately, you can perform a virtual index impact analysis.   
• The Test for Scalability validates how optimized SQL will perform under different concurrent user load scenarios and locates the SQL statement that offers the best scalability. This is done through SQL Optimizer's integration with Quest’s Benchmark Factory.
• Best Practices proposes common techniques to improve performance on your SQL statements by implementing database changes such as statistics update.

Global Indexing – Global Indexing, provides index recommendations for a SQL workload. You can submit multiple SQL statements including execution statistics, and Global Indexing provides a recommendation for a set of indexes (including virtual execution plan) that could improve the performance of all the analyzed SQL statements. This helps you evaluate whether the indexes would improve the SQL execution plans. You can decide to create the indexes and time the SQL statements to measure performance improvement, or perform a virtual index impact analysis.

Impact Analyzer – Impact Analysis helps you ensure reliable database performance by tracking execution plan and Oracle cost changes for SQL statements.  It keeps track of execution plan changes to allow you to estimate the impact on the SQL statements' performance due to database changes. You can simulate different database scenarios with a selected group of SQL statements that will give you a good representation of what will happen if a proposed database change actually occurred. Or, you can track the actual changes in the execution plan over time or as the result of actual changes in the database environment.