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 Mar 29, 2016

"INDEX ONLY" index scan should be used instead of tablespace scan when it performs better.

We were analyzing the optimization of the following query:

SELECT MAX(A.COL1)
FROM MY_TABLE A
WHERE
A.COL2= ?
WITH UR ;

There is an index that exists for MY_TABLE that has a first column of COL1 and a second column of COL2.

DB2 was using a tablespace scan to deliver the results of this query (even though this index was much smaller than the tablespace). We were able to rewrite the query in the following manner to accomplish a non-matching index scan to deliver the results:

SELECT A.COL1
FROM
MY_TABLE A
WHERE
A.COL2= ?
ORDER BY A.COL1 DESC
FETCH FIRST 1 ROWS ONLY
WITH UR ;

Using an non-matching index scan to deliver the results for this query resulted in significant performance improvement!

We would like to see DB2 make this decision without a manual rewrite.
  • Admin
    Janet Figone
    Reply
    |
    Sep 30, 2022

    Dear Larry, Thank you for submitting this enhancement request. The Db2 for z/OS developoment team has re-reviewed it and determined that we can not support this type of rewrite.

    They noted that what you have provided here might be cost model flaw that Db2 did not choose index-only for the first SQL. If you have the recreate docs for us to take a look at, we can try to see why index-only was not chosen for the first SQL.

    In the meantime, because we can not support this type of rewrite, we have dispositioned this idea to not under consideration.

    We appreciate your input to the Db2 for z/OS development team. We also hope that you will continue to submit ideas for improvements as customer feedback is a key component to shaping the future direction of Db2 for z/OS.

    Sincerely,

    Db2 for z/OS Team