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
Created by Guest
Created on Feb 5, 2018

Union all View (or common table expression of a UNION ALL) lead to HSJOIN

Case #0000086

Worked with developer and provided following explanation:
When there is a join between a UNION ALL view (or a common table expression of a UNION ALL) to another input (let's named it Z), to be able to utilize index access on the tables under the UNION ALL from the join columns (in this case, ACNT_ID from the tables SMB.MBA_TRDG_YEAR_xxxx), it is required that the input Z and the join predicates are rewritten to join with the tables directly. The most common use cases is when Z is a single table. In this reported query, Z is derived from a GROUP BY operation, hence it is not rewritten to join with the tables under UNION ALL view directly. Consequently, the join columns are not used to probe into the indexes, although index access method is chosen.
There are reasons Db2 does not rewrite when Z is a GROUP BY or any other operations. One is because those operations are need to re-computed for the join of each table under the UNION ALL, which could end up more costly than the original form.