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: http://ibm.biz/Data-and-AI-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: https://hybridcloudunit-internal.ideas.aha.io


Status Future consideration
Workspace Db2
Created by Guest
Created on May 20, 2021

A DB cfg parameter to set the default tablespace to prevent objects ending up in the wrong TS

When not explicitly set in the CREATE TABLE statement, a newly created table will end up in the last created tablespace.

A lot of customers have problems with this for several reasons.

  • They have no control over table placement when using a framework or application.

  • Several customers have not a dedicated DBA or enough knowledge so people are not aware of this construction until problems arise.

  • Some customers are not even aware of this effect.

  • If you create a tablespace for a certain use case, everybody else is impacted by this change if their DDL script is not explicitly mentioning the tablespace to be used.

  • Especially in MPP environments I have seen multiple cases of tables ending up in a tablespace only present on the head node while it should have been on all nodes.


So this issue creates a lot of rework if detected too late and possibly outages as well because of data skew (see last bullet).

Needed By Quarter
Needed by Date Jul 31, 2021