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 Not under consideration
Created by Guest
Created on Sep 5, 2019

Admin setting to limit tablespace used by rule output table or any table

I recently filled our IADB tablespace by inadvertently reversing rule logic when testing a rule definition. Because it is so easy to reverse rule logic when setting up the output table (meets or does not meet rule requirements), users could do this frequently. When I experienced this, I didn't even realize a table was being written to the IADB, and since it was a test, it wasn't registered in my project data sources, so I couldn't delete it. I discovered later that rerunning the test correctly dropped the table, but it doesn't reclaim space on the file system. That required intervention from a DBA. Further, I have found no documentation that explains this process, so I spent a long time figuring it out myself.

Needed by Date Sep 30, 2019