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
Created by Guest
Created on Feb 11, 2015

MQTs with REFRESH IMMEDIATE need to allow more flexible definitions(RIMS)

1. MQTs with REFRESH IMMEDIATE need to allow more flexible definitions. To make MQTs feasible for an environment where quick ingest and low data latency is a priority, they cant be REFRESH DEFERRED because of the excessive locking that occurs during either REFRESH TABLE or a user-managed load process. However, in order to define an MQT as REFRESH IMMEDIATE, a number of restrictions apply. These include the requirement to remove duplicate rows, the lack of support for inner joins, and the requirement to do aggregation. In many cases, we have had to break one MQT into multiple MQTs, for the sole purpose of avoiding the overhead of a REFRESH TABLE process. We have also had to add a number of otherwise unnecessary columns to the MQT definition just to guarantee uniqueness. Most frustrating of all, when MQTs are developed, we are nearly always playing reason code ping pong between all the various SQL20058N errors. Our requirement is to remove as many restrictions from REFRESH IMMEDIATE as possible in order to make MQTs a fully functional performance technique. PRIORITY: HIGH Angie Richey