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

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Not under consideration
Workspace Db2
Components BigSQL
Created by Guest
Created on Jan 15, 2018

Echo predicate functinality for sub queries

Issue Statement:

Echo predicate is not working properly to eliminate partition and query is taking longer time to complete

Filter With Hard Coded date: Query completes in 2 secs , since it is directly hitting the July 31st partition alone


Filter With Sub Query: Query took 8 mins to complete and we are facing performance issue.


Note: SELECT MAX(SNAPSHOT_DT) FROM ESA_QV_IL_DATAT1.MDM_IP à Query returned results in 42 seconds

Usually it will process sub query first and pass the latest date results to the outer sql, So that outer sql will process only for the filtered latest date. But here, it is doing nested loop join between these 2 tables for entire history and at last it is eliminating the latest date partition. so query is running for long time.

We like to include this feature in the product, so that it will improve performance in our process.