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: 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


ADD A NEW IDEA

FILTER BY CATEGORY

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

Showing 91

Ability to configure threshold for trigger to automatic resize(RIMS)

Some IT service providers for the financial industry in Germany have a high degree of automation. They are using AUTORESIZE for tablespaces. Unfortunately, the threshold cannot be specified and DB2 only extends the tablespace when it is full. In s...
over 7 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

RP Tables syntax

If the “INDEX IN” option is left off the index goes in the default TSP. There is no way to change this later
over 7 years ago in Db2 / Serviceability / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

Asynchronous activation

Design a new db2 database configuration variable to put the database available very quickly following an ACTIVATE command. As far as I understand, the database activation can last a long time due to the control of the tablespaces. It will be inter...
almost 8 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 1 Not under consideration

DB2 Partitioned Indices Order Preservation and Performance

GTECH is in the lottery and gaming business. They use DB2 as a competitive advantage in their offering. They are an IBM SW Reseller. They are always looking at new ways to leverage DB2, DB2 Blu, DB2 Merge/Backup,IBM Replication IIDR, to gain compe...
almost 8 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

EHL mode enhancement in pureScale.

Although the feature was enabled by mimicking a sysplex,, it is impossible to apply in the real world.The first reason is that the performance overhead is too much when switching from the not shared state to the shared stateSecondly, it is impossi...
over 4 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

evaluates sysdate for every row

The query db2 "select count(*) from TIR001.TITYPE where D_E_DEM_DEM=truncate(date(sysdate ) - (DAYOFWEEK(date(sysdate))) DAYS )" evaluates sysdate for every row
over 5 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

Partial indexes or functional index updates

We would like functional/partial indexes, that is indexes that include a where clause. Currently when there is an index that includes a condition we have to put the condition as part of a field (NAME_IS_BLANK) and then include that conditional fie...
almost 6 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

Compression of Primary Key Indexes with Version 10.1 FP 5

While doing some testing with, we noticed that when you create a table compressed, that ALL indexes automatically get compressed. We found out that we have the ability to specify "normal" indexes without compression, but you can not have an uncomp...
about 6 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 1 Not under consideration

DB level default table and index compression parameters

Have a database parameter for the default table compression type, and another for the default index compression type.
about 6 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

lock table partition in xxx mode

In batch jobs, to avoid lock escalation, customer needs to lock a table partition in exclusive mode, and run dml against this partition.
over 7 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration