Skip to Main Content
IBM Data and AI Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:


Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,


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


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com


ADD A NEW IDEA

Tables/Index (Range MQ MDC etc.)

Showing 93

Increase maximum numbers of columns in an index key from 64 to 120

Db2 has the lowest limit of allowed index columns compared to the competitors.
almost 6 years ago in Db2 / Tables/Index (Range MQ MDC etc.) 0 Not under consideration

ITC tables for pureScale

ITC are very useful to have table that have large batch deletes on it. Then space reclaim is a quite easy and fast task using REORG RECLAIM EXTENTS ONLY.
almost 6 years ago in Db2 / Tables/Index (Range MQ MDC etc.) 0 Not under consideration

Real global CGTT (not SESSION local)

SAP BW needs to materialize data into persistent (regular) tables to be able to access it from multiple session (connections). CGTT and DGTT in Db2 cannot be accessed from multiple sessions/connections. Therefore those temp tables that don't requi...
almost 6 years ago in Db2 / Tables/Index (Range MQ 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
almost 6 years ago in Db2 / Tables/Index (Range MQ MDC etc.) 0 Not under consideration

The support of IRS capture on pureScale EHL mode

In pureScale, Explicit hierarchical Locking is supported when opt_direct_wrkld set to ON.However, IRS capture is stopped abnormally due to SQL error.
about 6 years ago in Db2 / Tables/Index (Range MQ MDC etc.) 0 Not under consideration

EHL mode enhancement in pureScale.

Although the feature was enabled by mimicking a sysplex,, it is impossible to apply in the real world.The first reason is that the performance overhead is too much when switching from the not shared state to the shared stateSecondly, it is impossi...
over 6 years ago in Db2 / Tables/Index (Range MQ 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
over 6 years ago in Db2 / Tables/Index (Range MQ MDC etc.) 0 Not under consideration

Add the hidden attribute for index

我们希望给索引添加一个属性visible on/off比如:ALTER INDEX VISIBLE ON (默认属性)ALTER INDEX VISIBLE OFF (索引不可见)当索引不可见以后优化器无法使用不可见的索引,如果需要,直接alter index ...
over 6 years ago in Db2 / Tables/Index (Range MQ MDC etc.) 0 Not under consideration

The option ordinality is used in XML queries but the overall performance is very slow

We use the for ordinality option in our queries but the over all performance is very poor.There is a specific XSCAN needed when ordinality is specified which takes a long time. this XSCAN produces a sequence of XML ELEMENTS. This sequence is then ...
about 7 years ago in Db2 / Tables/Index (Range MQ MDC etc.) 0 Not under consideration

evaluates sysdate for every row

The query db2 "select count(*) from TIR001.TITYPE where D_E_DEM_DEM=truncate(date(sysdate ) - (DAYOFWEEK(date(sysdate))) DAYS )" evaluates sysdate for every row
about 7 years ago in Db2 / Tables/Index (Range MQ MDC etc.) 0 Not under consideration