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 90

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 Linux TECHNICAL ...
over 5 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

DB2 performance - Hash partition table

On the VLDB - Very Large Database environment.DB2 should support hash partition table to improve performance especially pureScale environment.
over 5 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 1 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...
almost 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

Support synchronous detachment of a table partition

Starting with DB2 9.7(?) the detachment of table partitions is handled asynchonously. To simulate synchronous behaviour a complicated work around has to be put in place. Such a behavior could be triggered by a new DML keyword such as ASYNC.
about 6 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under 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 pa...
about 6 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.
over 6 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 1 Not under consideration

BLU CDE Online REORG

Currently BLU CDE tables only have the RECLAIM EXTENTS option of REORG enabled. This does not physically move rows and therefore REORG cannot reclaim extents unless 100% of the rows in an extent have been deleted (via deletes or BLU updates). Also...
over 6 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) / BLU Acceleration 4 Future consideration

Wrap tables

Create a new type of table based on the size or on the time.create table packagevent (.... ) with history based 1 year on event_timestamp / 1Gb. It could be an ITC table. The oldest data / extent are automatically reused when new data is added and...
over 6 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

Asynchronous index rebuild on first access

Pain point: Index rebuild stops if user terminates the connection accessing the table with an index that is marked inconsistent and it starts over from the beginning again on next table access by another user. Scenario:An index object is marked in...
over 6 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration