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,
Post an idea
Upvote ideas that matter most to you
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.
using none unique index to accelerate update and delete on column-organized
there is a limitation (https://www.ibm.com/support/knowledgecenter/SSEPGG_11.5.0/com.ibm.db2.luw.admin.perf.doc/doc/r0061828.html) Update and delete operations that use an index scan on a column-organized table are not supported by the FETCH opera...
Temporal table support for column-organized tables
Currently, a column-organized table cannot be a temporal table because a PERIOD SYSTEM_TIME or PERIOD BUSINESS_TIME declaration is not supported in column-organized tables. This prohibits temporal data management with BLU. We request that column-o...
Allow data type ROW CHANGE TIMESTAMP in column-organized tables
We need the ability to define columns with data type ROW CHANGE TIMESTAMP in our tables so that we can track when the last change was made. Currently we use normal row based tables which allow this but we want to migrate to column based tables. Wh...
Improve performance of DB2 BLU SQL with the GROUP BY subquery
Our customer newly built the DWH system using DB2 BLU.But certain SQL's performance is extremely bad.Problem SQLs are with the GROUP BY subquery and the SET clause subselect.STSC says itâ€˜s a matter of architecture, not a problem and they offered...
BLU should tolerate Tools and Applications which are currently not BLU-aware
We currently employ with the introduction of db2 v10.5 BLU for our DWH. Our plan is to store almost all data in columns store. Just in exceptional cases tables should be stored row oriented. That's why we have set the registry variable DB2_WORKLOA...
As of DB2 for LUW Version 10.5 Fixpack 7, DB2 BLU still doesn't support non-unicode database, e.g. GBK. We need DB2 BLU to support database in codepage GBK, so that Chinese characters can be internally stored in double-byte, otherwise a data page ...
Support XA transactions on column-organized tables
We have a main DW database on DB2 for z/OS and a Datamart on DB2 for LUW. Some tables on both z/OS and LUW are populated using Cobol programs which are submitted from the mainframe. We want to convert the Datamart on DB2 LUW to BLU, but the Cobol ...
[Copy] 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...
Do not place IBM confidential, company confidential, or personal information into any field.