It's best practice to declare the foreign keys according to functional dependencies. E.g. if your other table is about salespeople, then its foreign key should refer to Salespeople.

Retaining an infinitude of Foreign Keys may cause future performance bottlenecks as transactional volume will get a performance hit by maintaining all those foreign keys and the indexes behind them.

Designers should seek a balance to avoid an excess. When only a sub-set of the foreign keys comprise the full primary key of the fact table, it is not unusual for developers, or query writers, to ...