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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Status Not under consideration
Workspace Db2
Created by Guest
Created on Nov 16, 2016

Improve access plan resolution for SELECT MAX() (or MIN()) statements on range-partitioned tables with local (partitioned)

Context: range partitioned table with partitioned indexes
A SELECT MAX() statement is issued on a field that is not the part of the partitioned key. The query is resolved by performing a full index scan on a partitioned index on that field.
That is, DB2 performs a complete index scan over all partitions and a sort to find the MAX().
We expect that DB2 would do the MAX() on each partitioned index object, and then pickup the MAX of all of them. This way a full scan is not needed and the IO/CPU cost and execution time would be greatly
  • Guest
    Jun 24, 2021

    this approach should also be evaluated not just for MIN() or MAX() function, but also, if user wants to get the first N set of rows, by using FETCH FIRST n rows clause..
    like
    select colum1 from tab1 order by 1 fetch first 50 rows.
    and similar limited range set of rows are involved,, should also be considered.