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,
Post an idea
Upvote ideas that matter most to you
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.
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.