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 95

Need to support inplace reorg on partitioned table with global indexes

This is critical in a 2 sense; 1) Performance The customer has many range-partitioned table with global indexes and most of them left unreorganized because INPLACE REORG on Inplace reorg on range-partitioned table with a global index is not suppo...
almost 5 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Future consideration

Release one restriction of pureScale

https://www.ibm.com/support/knowledgecenter/en/SSEPGG_10.5.0/com.ibm.db2.luw.admin.perf.doc/doc/c0009677.htmlIn a pureScale environment, space that is freed up by a delete transaction on one member may not be reused by an insert transaction on a d...
almost 5 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Delivered

Excessive DBHEAP by BLU compression dictionaries

In current design, when SQL statement accesses a table, the compression and expansion dictionaries of that table will be read into DBHEAP and kept there until database deactivation. For column-based table, the memory consumption may up to 100MB. i...
almost 5 years ago in Db2 / BLU Acceleration / 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 fi...
about 5 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

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