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,
Post an idea
Upvote ideas that matter most to you
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.
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
Do not place IBM confidential, company confidential, or personal information into any field.