Skip to Main Content
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:

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:

Status Not under consideration
Workspace Db2
Created by Guest
Created on Dec 2, 2014

Allow exclusion of columns from row compression to reduce overflows on updates

We have many large tables in our data warehouse that hold historized data records. There are four date columns:
- begin of visibility based on processing time (BAT_BEGIN)
- end of visibility based on processing time (BAT_END)
- begin of visibility based on effective date (WIT_BEGIN)
- end of visibility based on effective date (WIT_END).
On insert, a record always gets BAT_END = 9999-12-31 and WIT_END = 9999-12-31. When a newer record arrives, we update the old record with the BAT_BEGIN of the new record (WIT_END is a bit more complicated to set but for this RFE we can see it as similar).
The majority of the columns (about 60%) have BAT_END = 9999-12-31 and WIT_END = 9999-12-31, all other dates are a lot less often. In our eyes this leads to the fact that the 9999-12-31 gets very well compressed and other date values in this column need more space.
With adaptive row compression enabled (also previously with the "normal" row compression), we now get quite high overflow rates when we do the update of the BAT_END/WIT_END columns. And that leads to many necessary reorgs. We can for sure now set PCT_FREE to higher values but according to our tests it would need to be at a very high value, rendering compression quite useless.

If we could tell DB2 to not compress values in BAT_END/WIT_END columns, we could circumvent these problems. So we suggest to put a feature in a future release to define columns as not compressable.