IBM Data and AI

Welcome to the IBM Data and AI Ideas Portal for Clients!

We welcome and appreciate your feedback on IBM Data and AI Products to help make them even better than they are today!
Before you submit an idea, please perform a search first as a similar idea may have already been reported in the portal. If a related idea is not yet listed, please create a new idea and include with it a description which includes expected behavior as well as why having this feature would improve the service and how it would address your use case.
IBM Employees:
  • Our team welcomes any feedback and suggestions you have for improving our offerings / products! This forum allows us to connect your offering / product improvement ideas with IBM product and engineering teams.

  • If you have not registered on this portal please click on the following link and register. To complete registration you will need to open the email you will receive from Aha to confirm your identity.

Additional Information:
  • The shorter URL for this site is:

  • To view our roadmaps:

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

  • Please do not use the Ideas Portal for reporting bugs - we ask that you report bugs or issues with the product by contacting IBM support.

Allow Multi-Key Deletes from Parent Tables

Optim Data Growth currently has a restriction in place to disallow using a multi-key delete strategy on a Parent table. If you attempt to delete more than one key at a time, Optim will issue a severe warning code and then default the key limit to 1 single key.

Delete Process Warnings:

  "Table XYZ.dbo.MasterEventLog cannot support multiple key deletion. The table is a parent of a relational integrity constraint."

I'm not sure why Optim says it can't delete multiple keys at once from a parent table as that certainly is not a SQL Server (or other DBMS) restriction and seems like it's maybe some very old DBMS limitation.

Deleting a single key value at a time is a serious hindrance on performance and shouldn't even be an issue anyway since Optim deletes children before parents -AND- every DBMS engine has logic to ensure you won't orphan a child row. They don't care if your WHERE clause for a parent table Delete has one key or 100 keys; it will still verify zero child rows exist.

I opened a PMR for this performance issue and was told it has to be a RFE for whatever reason. The original PMR was 36324,082,000 if you need that for a reference. This would be a big win for performance improvement (something Optim needs on Deletes anyway) and it shouldn't be a big effort since this seems like an old edit left in place for whatever reason.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Feb 1 2019
  • Future consideration
Idea Priority High
  • Attach files

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions