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.
We use DB2 v10.5 DPF for a Warehouse Environment (40TB Data, ~9000 Users, 40 Tsd. Reports per day). We want to migrate the database to DB2 v184.108.40.206 BLU MPP with all tables column oriented. In this case we have checked the functionality for system...
Assuming that there is more than one temp tablespace with the same page size and 'IN TABLESPACE' clause is not specified in the DECLARE GLOBAL TEMPORARY TABLE command, then DB2 optimizer should allocate the temp tables across all temporary tables...
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 operat...
Support additional single-byte encodings for column-organized tables
The latest updates to DB2 have added the support of codepage 809 (ISO8859-1) for databases using column-organized tables..This is good for many Western customers, who are able to avoid switching to Unicode (and paying the penalty of 2x or 3x chara...
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...
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...
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...
Do not place IBM confidential, company confidential, or personal information into any field.