Saqib, you are correct. This appears to be a dependent child and is used to maintain the unit of work of the transaction represented in the link. You are correct in modeling it as such. Just make sure that it is included in your link hash string.
The caveat here is that manufacturer is not a business concept, that it meets the litmus test of a dependent child key (manufacturer id) (i.e., cannot stand alone and have meaning without the context of the relationship). If this is truly the situation, then it is a dependent child and should never be modeled as a hub, and as a DV2 standard should be included in the link object, not the satellite. We talked about this in class. Moving the dependent child to the satellite changes the grain of the relationship represented by the link. The standard for DV2 is to keep the unit of work together (the grain).
Also, with the Effectivity Satellite, don’t overload what the satellite represents by mixing meaning. The effectivity sat should be tracking the status of the relationship of the key set represented in the link. The team needs to be very clear about what a deleted flag actually means in the context of the Effectivity Satellite if you make the design decision to add it to the structure.
Sorry for the late response … I’ve been heads down in CDVP2 training for the last two weeks.
As your instructor, check your email for a little gift to help with all of this.
1 Like