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

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 a...
over 3 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) / BLU Acceleration 0 Planned for future release

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

List Partitioning

Allow to partition a table using a list of values (known as list partitioning).
over 7 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under 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

UNIQUE INDEXES over BIGINT column can't be compressed

unique indexes over id columns (bigint) are not compressed whereas the same unique index over decimal column gets compressedindex compression for unique indexes is urgently needed to reduce disk and memory footprint
about 7 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

Victimization of unused compression dictionaries from DBHEAP(RIMS)

Compression and Expansion dictionaries for each object (table, index) remain in memory until database deactivation time. This is problematic because enough DBHEAP must be allocated to host a compression/expansion dictionary for EACH object that is...
over 7 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

Parallel index creation for partitions of a partitioned-table(RIMS)

[JPMC EDW] Currently, a create-index statement with the PARTITIONED clause will process each partition sequentially. Ideally DB2 would perform this with some degree of parallelism. Currently, this can be accomplished by detaching the individual pa...
over 7 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

Allow more then 8bytes for DATABASE NAME.(RIMS)

Database names are currently limited to 8 characters (bytes) in size. This is painful when dealing with hundreds/thousands of databases.
over 7 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

Creation of range-partitioned tables during TRANSPORT

Whilst working on a recent pureScale POC with a customer, we came to the stage of upgrading their existing database to pureScale. Existing database had a catalog SMS tablespace. pureScale has a requirement that all tablespaces have to be AUTOMATIC...
over 7 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

Simplify shadow tables replication

Integrate the CDC engine in the DB2 engine and allow to configure the replication with SQL commands.
over 7 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration