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.
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 "email@example.com" 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