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 Dec 19, 2017

Give the option to make an index "invisible" to DB2

Sometimes, when I have added and index, I have had some surprises in the optimizer using that index when it should not. I would like a quick way to make the index "invisible" to the optimizer and make it not eligible for access paths until I specify for that to happen. It would be much quicker to "flip a switch" than to drop the index (and then have to rebuild it once again to have it used).
  • Guest
    Reply
    |
    Jan 15, 2020

    This would definitely help DBAs during program optimization, but I find even more important that:

    • it would prevent -904 errors during the create process (24x7 dynamic sql vs the time needed for rebuilding large indexes)
    • it would improve DevOpt process (takes off the risk of access path changes when nobody is watching, just because new indexes are created; we tend to avoid creating indexes as automated tasks because of this)