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.

Some database designers try to avoid such semantic issues by defining OrderID as non-nullable so that it must have a value, even when not part of the primary key. These designers then try to propose ...