What if you are in a modelling situation where you know you have dependent-child keys but you need to those partitions like a multi-active state of the business key? They are not composite keys (although business keys are rarely composite), but they do subcategorise the parent key.
I proposed this last year, https://blog.devgenius.io/partitioned-multi-active-satellite-4860af2d8846?sk=b419afd03a8a1689b96ac16b29bcb9fc
Benefits
- Less tables to join on
- Hubs remain representative of the business key (as defined by business architecture) and only the business key
- Simplifies the dv models with less tables to join on, reduced number of link tables
- Suites NoSQL platforms where joins are not particularly performant
Would you find this pattern useful?