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 updateson 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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
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...
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...
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...
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...
Rebuild BLU columnar dictionaries and recompress data in BLU columnar tables
An engineered capability is required to automatically rebuild an optimal BLU columnar compression dictionary and recompress BLU columnar tables. A technique is needed to easily rebuild and recompress columnar tables like we have for adaptive compr...
Currently we can create columnar tables with CLOB/LOB columns in it. What we can't do is reclaim the allocated diskspace of the CLOB/LOB columns (LOB_OBJECT_P_SIZE) in columnar tables
To get an idea about how many diskspace is allocated:
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...
Do not place IBM confidential, company confidential, or personal information into any field.