Data Management - Applications - C170 Performance Labs - uCertify

Data Management - Applications -
C170 Performance Labs - uCertify
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 Scheme - ER Model



Tables: Customer, DonutOrder, Donut - ✔✔Customer:

PK - CustomerID

, Rest are customer related fields



DonutOrder:

PK- DonutOrderID

FK - CustomerID

FK - DonutID

Rest of order related



Donut:

PK - DonutID

Rest are donut related



Relationships:

Customer - 1:n Non-identifying - DonutOrder

DonutOrder - n:1 Non-identifying - Donut



Why are the relationships in 2.1.1 Non-Identifying? - ✔✔The PK in DonutOrder is a unique key that
does not include FK of other tables.



3.2.1 - Creating a database



You need to create a database named "DonutOrderingDB". - ✔✔create database DonutOrderingDB;



3.2.2 - Dropping database in MySQL



You need to delete a database named DonutOrderingDB. - ✔✔drop database DonutOrderingDB;



3.2.3 - Understanding types of relationships



M:M - ✔✔B. Each record from first table is associated with many records in second table and one
record in second table is associated with many records in first table.