Same as Link for Dependent Child

Data Vault 2.0
, , , ,
1

Hello all,

We need to create a Same as Link for Dependent Child. Since dependent child are not Business Key and they only exist in LINKs, here is what we were thinking for the structure of the SAL:

HASHKEY_1
LINE_ITEM_1
HASHKEY_2
LINE_ITEM_2

Is this the right way to design Same as Link for a dependent child?

Thanks,
Saqib

2

I think you might be struggling with what a dep-key is.

Tell me, if it were not a SAL and just a link with two dep-keys in it would it not still just be a link?

SAL - is simply logical representation of a link nothing more, I feel you’re giving too much emphasis on dep-keys when they’re nothing more than better qualifying parent keys.

3

Hi @patrickcuba . So the answer is that this is the correct structure?

HASHKEY_1
LINE_ITEM_1
HASHKEY_2
LINE_ITEM_2

4

nothing wrong with what you’re proposing — it’s the wording that is a bit baffling
“Same as Link for Dependent Child” - there isn’t such a thing as SAL-dep-keys, you’re still building a SAL for same-as business keys — you’re only including dep-keys because they better qualify the bkeys, or you you need some ref code in the link that gives you more info about the relationship.

1 Like