Skip to Main Content
IBM Data and AI Ideas Portal for Customers

This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at

Status Not under consideration
Workspace Db2
Created by Guest
Created on Feb 10, 2015

new optimizer guideline to break CSE for a specific query or as a global guideline(RIMS)

Customer encountered scenario where use of CSE resulted in degradation in query performance (details below). This requirement is to implement a new optimizer guideline that will allow customer to break CSE for a specific query or as a global guideline. Wenbin: 'This behavior appears to be due to Common Sub Expression (CSE) functionality. The two Union branch queries both reference the view FDW.V_BSW_DERIVATIVES, and they both call F. F itself is a UNION view with two branches {F1, F2}. F1 is complex join under NLJOIN 12 (called F1), while F2 is simply a select from a single table FDW.V_BSW_DERIVATIVES_P3_2012. Now when compiling the UNION query, the optimizer makes FDW.V_BSW_DERIVATIVES a Common Cub Expression as TEMP 10. Our Query rewrite doesn't break that CSE as it is a UNION, this decision is because materialisation is generally good for performance in most cases. But when compiling query 2 alone, it's local predicates on F can eliminate branch F1 and leaves F2 to join with the outer two base tables.