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:



Tables/Index (Range, MQT, MDC, etc.)

Showing 96

Support mixed row/column environments without requiring CUR_COMMIT=ON

We have recently run into a problem when we enable Cur_commit because of the locking behavior expected by some applications (they expect blocking). Therefore, we have to disable CC, but then that app cannot use blu. We want to give our plant the...
about 3 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) / BLU Acceleration 0 Planned for future release

To remove tablespace maintenance restrictions on pureScale

To remove all the restrictions of SQL1419N Reason code = "11" on pureScale.11 Altering database containers is not supported in a DB2 pureScale environment. As a result, the following clauses are not supported with the ...
over 6 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 2 Functionality already exists

Use FSCR information to ommit empty data pages while performing Table Scan (TBSCAN)

ABSTRACT:Table scan over volatile table with large number of empty pages scans all empty pages instead of using FSCR to find pages to be scanned.VERSION INFORMATION:DB2 9.7.FP5 on Linux / DB2 9.7.FP9a on AIX 7.1 / DB2 10.5.FP4 on LinuxTECHNICAL IN...
over 5 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

Allow converting of the SYSCATSPACE to the reclaimable storage.

There is no way to convert the Catalog tablespace to RECLAIMABLE storage. The only workaround is to create a new database and to migrate the objects and the data. Since, we have a lot of databases which were created in pre-9.7 versions, we are stu...
over 6 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

Be able to DROP "restore pending" TABLESPACES supporting RP tables after RESTORE REBUILD

After RESTORE REBUILD of a slice of Prod DB into Pre-Prod DB, it is impossible to drop "Restore Pending" tablespaces supporting RP tables, you get SQL0282N. You can't detach "unrestored" partitions into junk either SQL0290N. So you are stuck and t...
over 7 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

Reorg: detailed information about Reorg incluiding a time/percent prediction to complete the all process

There is no way to find out how long the Reorg process or some steps will take, specially for big tables.
about 2 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

Truncate table partiton

1. many customers expect to truncate a table partition without first detach and then drop, and finaly add a new partition with the same definition as the detached partition, because they may design their range partition as "Jan, Feb, ... Dec" with...
about 7 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

XML Schema 1.1

DB2 PureXML does not support XML Schema Version 1.1, although it would be very useful. XML Schema Version 1.1 goes far to correct numerous inadequacies in XML Schema Version 1.0 for extensibility of data models in order to meet future needs.
about 6 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 1 Not under consideration

IBM.ENtityFramework.Core To Scaffold Indexes Properly

We used latest released IBM EF Core nuget packages to add DB2 Support to our application with existing DB2 database. Scaffolding the DB out to Models and usable DBContext time and again. We realized on comparing DB2 server that 90% of the indexe...
over 1 year ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Future consideration

Lock data partition

Currently it is merely possible to lock a complete table by means of the "lock table" statement. However, for range partitioned tables, it would be beneficial to be able to lock a specific data partition.That is, a statement like: “lock data par...
almost 6 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration