SQL Optimizer for IBM® DB2® LUW 5.0
Release Notes
Thursday, October 16, 2025
About SQL Optimizer for IBM® DB2® LUW
SQL Optimizer for IBM® DB2® LUW maximizes SQL performance by automating the manual, time-intensive and uncertain process of ensuring that SQL statements are performing as fast as possible. SQL Optimizer for IBM® DB2® LUW analyzes, rewrites, and evaluates SQL statements within multiple database objects, and files. Whether you are a developer, DBA, or performance tuner, you can let SQL Optimizer for IBM® DB2® LUW analyze and optimize all the problem SQL from multiple sources. SQL Optimizer for IBM® DB2® LUW also provides you a complete index optimization and plan change analysis solution, from index recommendations to simulated index impact analysis, through comparison of multiple SQL access plans.
New in This Release
DB2 LUW client and server versions support
DB2 LUW 11.1, 11.5, 11.5.9, 12.1
Operating System support
-
Microsoft Windows 11
-
Microsoft Windows Server 2022
Deprecated Operating Systems and Databases
The following operating systems or databases are deprecated in the current release:
-
Microsoft Windows 7
-
Microsoft Windows 8
-
Microsoft Windows 8.1
-
Microsoft Windows Server 2008 r2
-
Microsoft Windows Server 2012
-
Microsoft Windows Server 2012 R2
-
DB2 LUW Client 9.5
-
DB2 LUW Server 9.5
Resolved Issues and Enhancements
The following is a list of issues addressed and enhancements implemented in this release of SQL Optimizer for IBM® DB2® LUW:
| Resolved Issue or enhancement | Defect ID |
|---|---|
| Users are unable to use the trial license of SQL Optimizer for DB2 LUW. The application displays the error Trial license expired on 4/25/2022 when the product is installed. |
SOFUL-275 |
| The SQL Optimizer for DB2 LUW now allows users to specify preferred schema(s) when generating explain plans. If multiple schemas contain plan tables, the optimizer will use the plan tables from the first listed schema and drop the plan tables from the Current Schema. By default, the SYSTOOLS and CURRENT_USER schemas are pre-populated in the entry field. | SOFUL-274 |
| The SQL Optimizer for DB2 LUW 64-bit is not necessary when connecting to a DB2 Client over SSL port 50003. For additional details, see the Quest knowlege base article Is SQL Optimizer for DB2 LUW 64-bit required for an SSL connection? | SOFUL-260 |
| SQL Optimizer for LUW displays explain plan table error Invalid plan table(s) definition; it may not match with current DB2 LUW version when connecting to DB2 LUW version 11.5.7 or above. | SOFUL-256 |
Known Issues
The following is a list of issues known to exist at the time of this release.
| Feature | Known Issue | Defect ID |
|---|---|---|
| General | Column detection of table functions with host variables or columns as table function parameters are not supported. These columns will be defined as host variables. | N/A |
| SQL Optimizer |
A SQL statement cannot have more than 2047 characters on one line in the SQL Text pane in the SQL Optimizer or the Index Expert function due to a size limitation of the SyntaxMemo component used for editing. Workaround: Format a large SQL statement so that it is on several lines. |
N/A |
| SQL Repository |
In the SQL Repository, when you refresh the access plan of a SQL statement that uses a temporary table, the temporary table must exist in order to retrieve the current access plan. If the temporary table does not exist, SQL Optimizer for IBM® DB2 LUW prompt you to create the table and then copy the DDL for creating the table to the User-Defined Temp Table module so you can create the table. (This works correctly.) If a temporary table does exist, it checks to see if the table definition for the existing table is the same as the one needed to refresh the plan. If it is the same, it should use the temporary table that already exists. Instead it prompts you to create the table and then fails when you try to create the table. Workaround: Manually remove the temporary table in the User-defined Temp Table module before you refresh the access plans. |
ST39369 |
| Engine |
An error message displays when you try to get a plan for a SQL function with a variable parameter. Workaround: replace the function with a variable parameter with a variable. |
ST92002 |
System Requirements
Before installing Quest SQL Optimizer for IBM® DB2® LUW , ensure your system meets the following minimum hardware and software requirements:
| Platform | 1 GHz recommended minimum |
| Memory | 1 GB of RAM recommended minimum |
| Hard Disk Space | 50 MB hard disk space |
| Operating System |
Microsoft Windows 10 (32-bit and 64-bit) Microsoft Windows 11 (32-bit and 64-bit) Microsoft Windows Server 2016 Microsoft Windows Server 2019 Microsoft Windows Server 2022 |
| Database Client | PC client connection to DB2 LUW with DB2 LUW Client Software version 11.1, 11.5, 11.5.9, 12.1 and higher |
| Database Server | DB2 for LUW 11.1, 11.5, 11.5.9, 12.1 and higher on Windows, UNIX, OS/2, Linux, AIX, HP-UX, Solaris platform |
| Additional Software |
Adobe Acrobat Reader 2020 or later (for viewing the Installation Guide) Microsoft Edge 140 or later |
Virtualization Support
| Application Virtualization |
Limited testing has been performed for Citrix XenApp 6.5 on Windows Server 2008 R2. |
|
Note: SQL Optimizer for IBM®DB2® LUW may work in virtualization environments other than the ones in which it was tested. | |
Getting Started with SQL Optimizer for IBM® DB2® LUW
Contents of the Release Package
The Quest SQL Optimizer for IBM® DB2® LUW release package contains the following products:
- Quest SQL Optimizer for IBM® DB2® LUW
-
Product documentation, including:
- Help (including tutorials)
- Quest SQL Optimizer for IBM® DB2® LUW Installation Guide
Installation Instructions
Refer to the Quest SQL Optimizer for IBM® DB2® LUW Installation Guide for installation instructions.
Additional Resources
Get the latest product information, find helpful resources, and join a discussion with the SQL Optimizer for IBM® DB2® LUW team and other community members. Click here to join the SQL Optimizer for IBM® DB2® LUW community.
Global Operations
This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.
This release supports any single-byte or multi-byte character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.
This release has the following known capabilities or limitations: (same as that in version 2.8.0).