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

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
over 6 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 i...
almost 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...
almost 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.
almost 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 ...
almost 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.
almost 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

Block locking for U/D on MDC when LOCKSIZE=BLOCKINSERT

Block locking is done for INSERTs on MDC tables when LOCKSIZE = BLOCKINSERT, which is a great benefit for memory usage, and allow to parallelize treatments for different dimensions. However, this is unsufficient, because treatments do also Update/...
about 3 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

Declarative RI for Db2 LUW Bitemporal tables

it would be good to implement Bi-temporal Period Containment with declarative RI in Db2 LUW
over 3 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration

BID lock avoidance on MDC tables

2 DMLs working on different dimensions on MDC can lead to deadlock when this should not happen.Ref: case TS000003442
about 4 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Not under consideration