Multi Active Satelite or Normaization needed?

Hi guys,

first question here (i’m a data vault beginner :slight_smile: )

Imagine having a source table with the following data

|Client ID |Rating agentur (A/B) |Rating method (L/S) |Trustful (Y/N) |Raing data |Rating (1-10)|

|1 |A |L |Y |01.01.2025 |3|
|1 |A |S |Y |01.01.2025 |5|
|1 |B |L |N |15.01.2025 |2|
|1 |B |S |N |16.01.2025 |9|
|2 |A |L |Y |03.01.2025 |7|
|2 |A |S |N |06.01.2025 |7|
|3 |A |L |Y |13.02.2025 |6|
|3 |A |S |Y |19.02.2025 |5|
|3 |B |S |N |13.02.2025 |8|

My business key is the Client ID, but unfortunately the granularity of the table is not fitting to the HUB Client ID.

My aim was to create one hub (BK Client ID) and one sat (all the other fields).

Is there a way to match SAT’s and HUB’s even if the granularity is not matching?

Looks like the table formatting messed up: this might be a little easier to read

Client ID Rating agentur (A/B) Rating method (L/S) Trustful (Y/N) Raing data Rating (1-10)
1 A L Y 01.01.2025 3
1 A S Y 01.01.2025 5
1 B L N 15.01.2025 2
1 B S N 16.01.2025 9
2 A L Y 03.01.2025 7
2 A S N 06.01.2025 7
3 A L Y 13.02.2025 6
3 A S Y 19.02.2025 5
3 B S N 13.02.2025 8

I think you’ve grasped the issue and your options pretty well imo. You’ve either got to use a multi-active-satellite to get the grain you want or introduce another entity that resolves the grain issue.

I hope it’s your first question of many! Welcome to the forums

All the best,
Frankie

to help you decide , The Different Grains of Multi-Active Records. | by Patrick Cuba | The Modern Scientist | Medium

Hey @Dorry,
Welcome to this forum.
Not knowing your business, Rating Agency, and Rating Method are business objects, too. I expect further attributes about those two, shouldn’t I?
That would make this a satellite on a Link with the Unit of Work (UOW) Client-Agency-Method.
There may be no further Multi-Activity. If yes, it seems you’re lucky because there is a proper type code to get a natural primary key, which is easier to handle than a generated sub-sequence.
Warm regards
Volker

Before deciding what is a business object / entity, discuss with the business.
Likely a method is not a business object, just a concept, maybe even something that extends into a code+description (reference data).
Rating agency does sound like a business object (confirm).
I’m in favour of LESS DV tables, not more, hence the link to the article I shared above.