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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Data & AI Roadmaps ( - Use this site to view roadmaps for Data & AI products.

IBM Employees should enter Ideas at

Status Not under consideration
Workspace Db2
Created by Guest
Created on Sep 1, 2020

Allow table compression to be disabled for DGTTs and CGTTs

In short: OLTP applications frequently encounter performance issues because DB2 enables table compression by default for all DGTTs / CGTTs.

Details from a real-time example:

When inserting 40K rows to a DGTT, it takes 2 seconds.

When we immediately insert another 40K rows to the same DGTT using the same INSERT statement, it takes 0.08 seconds.

This has nothing to do with caching. It is because compression is enabled by default for all DGTTs / CGTTs and this is the overhead of generating the compression dictionary.

DB2 only generates the compression dictionary if a certain amount of data is inserted (based on my tests, this was around 25K rows). The same applies to CGTTs.

What this means is that any proc which inserts > 25K rows (approx.) into a DGTT / CGTT will incur this significant overhead every time it is executed.

So procs that should take 0.08 seconds to execute will consistently take 2 seconds.

Most OLTP applications create small (and short-lived) temporary tables and therefore don't benefit from table compression. Having the ability to disable table compression will significantly improve query performance in many cases.

Needed by Date Dec 31, 2020