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 89 of 12684

IBM.ENtityFramework.Core To Scaffold Indexes Properly

We used latest released IBM EF Core nuget packages to add DB2 Support to our application with existing DB2 database. Scaffolding the DB out to Models and usable DBContext time and again. We realized on comparing DB2 server that 90% of the indexe...
about 1 year ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 0 Future consideration

Truncate table partiton

1. many customers expect to truncate a table partition without first detach and then drop, and finaly add a new partition with the same definition as the detached partition, because they may design their range partition as "Jan, Feb, ... Dec" with...
almost 7 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.
almost 6 years ago in Db2 / Tables/Index (Range, MQT, MDC, etc.) 1 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

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/...
almost 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

List Partitioning

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