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 Submitted
Workspace Db2
Components Db2 on-premise
Created by Guest
Created on Feb 20, 2026

Improve early exit/early close SQL processing in partitioned environments

In partitioned Db2 environments (MPP), where SQL statements are processed in parallel by multiple partitions and multiple agents on each of them, certain SQL might execute much longer due to processing a section of an SQL (and access plan) that could be avoided or interrupted early in runtime. For example, with certain joins, the inner side of the join might not need to be executed at all if there is no row on the outer.

In serial (SMP) configurations, due to sequential processing, possibly unnecessary inner side processing (that might be a large, intermediate result set) this is avoided "by design".

In MPP both sides of the joins are processed in parallel, that, in general, is beneficial performance-wise, but might impose an extra processing time for certain edge scenarios (like one outlined before).

 

Currently MPP Db2 is able to stop/close executing sections of the plan that don't need to produce any (or more) rows for SELECT queries, but it doesn't seem to be the case for INSERTs (and possibly UPDATEs and DELETEs)

Needed By Quarter