I am new to formal data modeling and TDM. Excuse me if I am asking a simple question.
I create a Logical model with a few entities, with simple one-attribute primary indices. And I declare some of them to have one-to-many relationships.
Where there is a hierarchy of relationships, I get a behavior I am surprised by when trying a Logical-to-Physical conversion (I chose SQLServer 2005).
Physical tables created as a child in a relationship hierarchy are given not only the parent entity’s primary key as a column, but also the parent’s parent’s primary key (and parent’s grandparent, if applicable, etc.)
Is this a natural result of formal data modeling?
Or is it a part of this tool?
Can I influence this behavior in the tool?