Data Management - Applications - C170 Performance

1.1.1 - Conceptual Schema - ER Model Tables: Customer, DonutOrder, Donut - Customer: PK - CustomerID Rest are customer related fields DonutOrder: FK - CustomerID, FK - DonutID Qty, SpecialNotes Donut: PK - DonutID Rest are donut fields Relationships: Customer - 1:n Identifying - DonutOrder DonutOrder - n:1 Identifying - Donut Why are the relationships in 1.1.1 Identifying? - The PK's of Customer and Donut are included in the composite primary key of DonutOrder. 2.1.1 - Physical ...

1.1.1 - Conceptual Schema - ER Model Tables: Customer, DonutOrder, Donut - Customer: PK - CustomerID Rest are customer related fields DonutOrder: FK - CustomerID, FK - DonutID Qty, SpecialNotes Donut: PK - DonutID Rest are donut fields Relationships: Customer - 1:n Identifying - DonutOrder DonutOrder - n:1 Identifying - Donut Why are the relationships in 1.1.1 Identifying? - The PK's of Customer and Donut are included in the composite primary key of DonutOrder. 2.1.1 - Physical ...

1.1.1 - Conceptual Schema - ER Model Tables: Customer, DonutOrder, Donut - Customer: PK - CustomerID Rest are customer related fields DonutOrder: FK - CustomerID, FK - DonutID Qty, SpecialNotes Donut: PK - DonutID Rest are donut fields Relationships: Customer - 1:n Identifying - DonutOrder DonutOrder - n:1 Identifying - Donut Why are the relationships in 1.1.1 Identifying? - The PK's of Customer and Donut are included in the composite primary key of DonutOrder. 2.1.1 - Physical ...

Data Management - Applications - C170 Performance Labs - uCertify 1.1.1 - Conceptual Schema - ER Model Tables: Customer, DonutOrder, Donut ans: Customer: PK - CustomerID Rest are customer related fields DonutOrder: FK - CustomerID, FK - DonutID Qty, SpecialNotes Donut: PK - DonutID Rest are donut fields Relationships: Customer - 1:n Identifying - DonutOrder DonutOrder - n:1 Identifying - Donut Why are the relationships in 1.1.1 Identifying? ans: The PK's of Customer a...