True.

This is a non-production "research" ETL database.

The table in question won't ever be updated by a "end user" so to speak.

However, your point is valid...

I may look at dropping the FK constraints since this is being loaded via an ETL operation additional indexes just create overhead and the ETL process should never encounter FK violations in the first place (...in theory....) 🙂