Welcome to Embarcadero® DB Optimizer&trade XE Pro 2 (version 3.0)

Published April 21, 2011

DB Optimizer Home | DB Optimizer Documentation | Embarcadero Technical Support | www.embarcadero.com


Thank you for using Embarcadero DB Optimizer, an enterprise SQL development and optimization tool that gives database developers and administrators the perfect environment for building the best performing SQL code. This application easily identifies inefficient SQL code and boosts developer productivity by ensuring SQL is right before it becomes a problem in mission-critical applications. DB Optimizer also provides a rich SQL IDE with code completion, real-time error checking, code formatting and sophisticated object validation tools. Lastly, DB Optimizer provides advanced project and data source management tools.

DB Optimizer is supported on the following operating systems:

DB Optimizer requires a Java5 VM to run:

SQL execution and SQL tuning with DB Optimizer is supported on the following DBMS platforms and versions:

SQL profiling with DB Optimizer is supported on the following DBMS platforms and versions:

DB Optimizer should be installed in a different directory than previous versions of DB Optimizer. If DB Optimizer is installed in the same directory, the following error will result in at application start up: "Unable to read workbench state. Workbench UI layout will be reset.” Additionally, DB Optimizer should be installed in a different directory than previous versions. If a previous version is already installed on your machine, either change the default Workspace or delete all files from the Workspace directory. The Workspace directory location appears whenever you start Optimizer, and can be redefined from this dialog box. If the same Workspace is indicated for the new version as was indicated previously, the following error will result: “Cannot restore workbench layout". If DB/Optimizer is already running, you can also modify the Workspace directory by choosing File > Switch Workspace > Other from the Main Menu.

Note: DB Optimizer does not access in any way, shape or form any of the information, tables or views licensed under Oracle's diagnostic pack.

What's New in DB Optimizer 3.0

Improvements to Profiling

Improvements to Tuning

Release Notes

DBMS Support

Important Advisory Notes

Bug Fixes

What's New in DB Optimizer 3.0

User Interface Changes

Object Indexing Enabled by Default

Previous versions of DB Optimizer had the option to create an index of schema objects on a data source in order to provide code completion and semantic validation of object names in the SQL Editor, but this was disabled by default, because it could affect data source performance. In DB Optimizer 3.0, the speed and efficiency of Object Indexing has been significantly improved, so this functionality is now enabled by default. This option can still be disabled from the preferences window (available from the Preferences > Data Source Indexing option).

New Actions on Oracle Sessions During Profiling

While profiling an Oracle data source, the Sessions tab in the profiling editor has two new context menu actions on rows in the session grid:

MS SQL Server and Sybase ASE Profiling Improved

Profiling on Microsoft SQL Server and Sybase Adaptive Server Enterprise are now more efficient, contributing less than 2% load on the profiled data source under most conditions. Furthermore, more accurate data is collected.

Improved User Interface for the Tuning Editor

The dedicated Input tab of the Tuning Editor has been removed, allowing the user to specify statements for tuning directly within the Overview tab. In the top-right of the Tuning Editor, there is an input selection button, to add statements for tuning from the following sources:

To view or modify a tuning statement, or to bind variable values within the statement, double-click on the statement in the grid or right-click and select Edit. from the context menu.

Oracle RAC Profiling

All instances of an Oracle Real Application Cluster (RAC) can be profiled using a single profiling session (and a single connection to the cluster). To enable this functionality for a RAC data source, you must access the Profile Configurations dialog, in one of the following ways:

Within the Profile Configurations dialog, check the box for Real Application Cluster (RAC) mode. Within a RAC profiling session, the filter bar at the top of the profiling editor includes an Instances filter, which allows you to view profiling results for individual instances in the cluster, or show results for sessions from all cluster instances. Furthermore, several tabs from the Profiling Details view will show the ID of the instance on which the selected statement/event/session was observed.

Profiling Alerts

During profiling, alerts can be triggered based on thresholds set on the number of:

These alerts can produce a system notification (from the Windows status tray) and/or generate an email to be sent to one or more addresses. This allows you to begin a profiling session, continue with other work, and return to DB Optimizer when the alert has fired to investigate the underlying cause. Alerts can be set up from the preferences page available from the menu item at Preferences > Profile Alerts. Alerts may be configured per data source and multiple alerts may be configured for a profiling session. In order to generate email messages for alerts, the mail server options must be specified on the Email Settings page under the Profile Alerts preferences, and one or more recipients must be specified on the Email Contacts page.

Profiling Reports

The results of a profiling session can now be exported as an HTML or PDF document that can be saved for later, shared, and printed. Within the Profiling Editor, the Export Report button is located in the top right, between the filter options and the Help button. By default, the report is generated for the entire duration of the profiling session. To restrict the report to a particular time interval, click and drag on the profile session chart. To clear the selection, click once on the chart outside the selection.

Support for Common Table Expressions on Oracle and MS SQL Server

The SQL Editor and Tuning Editor now both support common table expressions (CTEs) for Oracle and SQL Server. This includes syntax highlighting and checking in the editor, as well as generation of explain plans for CTEs from the SQL Editor and the Tuning Editor.p>

Improved Visual SQL Tuning for Oracle

The Visual SQL Tuning (VST) diagram for Oracle 10g and 11g now has the option of showing Explain Plan details in addition to the column relationships. The explain plan display can be toggled on/off by clicking the leftmost button that appears when hovering over the SQL Analysis diagram. The additional nodes shown in the Explain Plan overlay provide details on the flow of the query plan, with operations (such as nested loops, sorts, and joins) showing connecting tables and other operations.

Release Notes

DBMS Support

Important Advisory Notes

Bug Fixes

Use your browser Find feature to locate a particular bug number or click a link below to see the issues addressed in a specific build.

Bugs Fixed in DB Optimizer 3.0

Bugs Fixed in Embarcadero DB Optimizer 3.0
OPT-2642 Profiling Details for a DB2 data source now correctly reports elapsed time in the Execution Statistics section of the Profiling Details tab.
OPT-2646 Performance of a tuning job for an Oracle 9i data source has been increased. Semantic validation and query analysis are now performed more efficiently.
OPT-2647 Error in tuning job while generating cases, "object caching: could not retrieve the following object because it doesn't exist or is not qualified properly: object name" no longer displayed.
OPT-2668 The Profiler now correctly uses SYSTDATE for Oracle 8 and SYSTEMSTAMP for Oracle 9 and higher.
OPT-2696 On Oracle 9, tuning performance and semantic validations of constraint queries has been inproved.
OPT-2716 SQL Parser no longer displays error "Encountered Unexpected Token" when tuning well formed SQL.
OPT-2779 TOP keyword in Sybase 12.5.3 and higher is now recognized by the SQL Parser.
OPT-2782 Sybase object resolution no longer fails for databases created by users with SA_ROLE when tuning as sa.
OPT-2786 Tuning error for SQL Server 2008 that appeared when the database was created by a user with SA_ROLE who is not the sa, has been fixed.

Additional Resources

Licensing Your Embarcadero Technologies Product

All Embarcadero Technologies products include a 14-day trial period. To continue using the product without interruption, we recommend that you license it as soon as possible. To license your product, use the License Request Wizard found in the Help menu of your respective product. If you have not yet purchased your Embarcadero Technologies product, contact sales@embarcadero.com, or uk.sales@embarcadero.com for sales in the EMEA region.

Embarcadero Technologies Product Support

The Embarcadero Technologies Web site is an excellent source for additional product information, including white papers, articles, FAQs, discussion groups, and the Embarcadero KnowledgeBase. Go to www.embarcadero.com/resources, or click any of the links below, to find:

Embarcadero Technologies Technical Support

If you have a valid maintenance contract with Embarcadero Technologies, the Embarcadero Technical Support team is available to assist you with any problems you have with our applications. Our maintenance contract also entitles registered users of Embarcadero Technologies products to download free software upgrades during the active contract period. Evaluators receive free technical support for the term of their evaluation (14 days).

We encourage you to open technical support cases via the Technical Support request form at the Embarcadero Technologies Web site. For additional information about Embarcadero Technologies Technical Support, go to the Support page on our Web site.

Embarcadero Technologies on the Web

To download evaluations of other Embarcadero Technologies products or to learn more about our company and our products visit us at www.embarcadero.com.