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 (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 Not under consideration
Workspace Db2 for z/OS
Created by Guest
Created on Feb 17, 2020

Allow SQL to reference a Temporal table and Transparent archiving table in the same statement

We have adopted widespread use of System Time functionality on our application tables.  We have need to use transparent archiving as well, since we have table where data churn is significant and we don't have need to track row changes - just the final state of the row once it's removed from the processing table.

However, we discovered recently a limitation that disallows referencing both a System Time temporal table and a transparent archiving enabled table in the same SQL statement.  With our widespread use of system time, this essentially blocks our ability to use transparent archiving, as there will almost always be a join between tables of these two types.

I know one solution is to use system time with the 'ON DELETE ADD EXTRA ROW' option instead of transparent archiving; however, the two functions work differently and for different reasons.  As stated above, we don't need the additional functionality that system time provides.

This was a shocking find and I'm not sure I understand why the two features won't work together.  A significant limitation.