Skip to Main Content
IBM Data and AI Ideas Portal for Customers

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:

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

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps:

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is:

Status Planned for future release
Created by Guest
Created on Aug 31, 2017

Enhancements to OQWT Query Advisor

We use OQWT advisors regularly for both reactive and more common proactive performance review
The DSM tool seems to be working fine, although we really need the query and Access path advisors to work. One of my concerns with the advisors (OQWT (DSM or DS) is that there are times, when their recommendations, although good possible solutions are not always the
best solution. We ran advisors for a query that uses a subselect for a column comparison and there were only stats advisors and one AP advisor recommendation. We ended up finding out own solution "old school". and converted the subselect to a CTE which resulted in a 99% reduction in I/O and CPU. For this query, this was the best solution and worked exactly the same in all of our 23 production subsystems.
  • Admin
    May Chu
    Oct 9, 2020
    This is something to consider for our future release