This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
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,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
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.
Do not place IBM confidential, company confidential, or personal information into any field.