Database Reference
In-Depth Information
For the first scenario, I would embed
Account
into
Customer
because, based on the re-
quirements statement, it appears
Customer
and
Account
are frequently queried together.
Also,
Account
has no other relationships, so embedding
Account
into
Customer
should
not increase complexity. We would have to confirm this, but there is a good chance that a
Customer
owns, on average, just a few
Accounts
and therefore there should be minimal
redundancy as well.
For the second scenario, because we are focusing on getting the data in to the system (data
entry) instead of querying the system, we would like to minimize redundancy. Therefore I
would not embed
Order Line
into
Order
. I am further confident in this decision to keep
them separate based on the large size of both concepts and the high cardinality relationship
between them (an
Order
on average contains 20
Order Lines
).
