The Unique Key Index is e.g. SYSTEM_CODE, PROJ_NAME.
SYSTEM_CODE is a foreign Key column and now also gets an index containing SYSTEM_CODE.
It would have been adequately serviced by the UK index, since SYSTEM_CODE is the leading column.
There are no creation errors and that is why my subject states 'logically' duplicate indexes in that the second index is superfluous and unnecessary maintenance overhead & space requirement for the DB.
I would like the tool to recognise that or worst case give me an option to flag that foreign key/index as unnecessary. But the tool being clever is the first option!
I see Philip has logged a bug on this, you could perhaps see what that bug states?
Thank you & regards