Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform 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 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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

IBM Employees should enter Ideas at https://ideas.ibm.com



Status Under review
Workspace Db2
Components Db2 Warehouse
Created by Guest
Created on Dec 2, 2025

System temporality slowness on Db2wh

System temporal tables are part of the type two of slow changing dimensions, this assists in tracking changes that happens on the data by preserving historical accuracy.

These tables have two tables, The BASE table and the HISTORY table. When records get deleted or updated the records will go from the BASE table to the HISTORY table.

The issue with system temporality on Db2wh is that for big updates and deletes, they run way longer because they have to move multiple records from BASE to HISTORY. IBM once gave us a solution to create a TABLESPACE in one partition and create the HISTORY table on that TABLESPACE. We tested this solution some time last year and the performance improved drastically on deletes and updates, but the only concern is around extracting the data from the HISTORY table since all of the data will now be sitting on one partition instead of 24 partitions, so that solution solves one problem and causes another issue.

Can we have a fix that can:

have the history table defined on multiple members with expected performance and so that SELECTs on history tale won't be impacted.

Needed By Week