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
Workspace Db2
Created by Guest
Created on Oct 8, 2019

Primary Keys should allow NOT TRUSTED

Currently you can create NOT ENFORCED primary keys but the optimizer will then always treat these as trusted. This causes problems when the constraint is violated but a filter includes all PK columns since the engine will return only one row even though multiple rows may exist.

Needed by Date Oct 8, 2019
  • Guest
    Feb 4, 2020

    We are migrating from Netezza to IIAS. We were glad to see that on DB2 we could use ENFORCED primary/unique keys to avoid duplicates. Unfortunately we've hit performance issues with our ETL workflows and we were advised to drop the enforced constraints.
    So we've started using UNFORCED primary/unique keys and we run a script to check these constraints ourselves after the ETL workflows. Our reporting tools also use this keys to link tables.
    Now our script notifies us that we have duplicates in some tables. But when we want to consult these lines in our query tool, we don't get to see these duplicates...
    Very annoying and inconvenient!

  • Guest
    Jan 31, 2020

    Hungarian customers (3 of them) are asking the same

  • Guest
    Jan 31, 2020

    Japanese Netezza customers hit this issue, and are in critical situation... Some of them use PK with duplicated value for information column.  At least four customers suffer from this incompatibility.  Please let primary keys allow "NOT TRUSTED" to avoid returning incorrect results.

  • Guest
    Dec 9, 2019

    The customer BNP Paribas / Cardif is asking the same

  • Guest
    Oct 8, 2019

    There is some discussion on Slack on this.  E.g.