Database Relations
Using the INVOICE table structure shown in Table, do the following:
|
ATTRIBUTE NAME
|
SAMPLE VALUE
|
SAMPLE VALUE
|
SAMPLE VALUE
|
SAMPLE VALUE
|
SAMPLE VALUE
|
|
INV_NUM
|
211347
|
211347
|
211347
|
211348
|
211349
|
|
PROD_NUM
|
AA-E3422QW
|
QD-300932X
|
RU-995748G
|
AA-E3422QW
|
GH-778345P
|
|
SALE_DATE
|
15-Jan-2016
|
15-Jan-2016
|
15-Jan-2016
|
15-Jan-2016
|
16-Jan-2016
|
|
PROD_LABEL
|
Rotary sander
|
0.25-in. drill bit
|
Band saw
|
Rotary sander
|
Power drill
|
|
VEND_CODE
|
211
|
211
|
309
|
211
|
157
|
|
VEND_NAME
|
NeverFail, Inc.
|
NeverFail, Inc.
|
BeGood, Inc.
|
NeverFail, Inc
|
ToughGo, Inc.
|
|
QUANT_SOLD
|
1
|
8
|
1
|
2
|
1
|
|
PROD_PRICE
|
$49.95
|
$3.45
|
$39.99
|
$49.95
|
$87.75
|
a. Write the relational schema, draw its dependency diagram, and identify all dependencies, including all partial and transitive dependencies. You can assume that the table does not contain repeating groups and that an invoice number references more than one product. (Hint: This table uses a composite primary key.)
b. Remove all partial dependencies, write the relational schema, and draw the new dependency diagrams. Identify the normal forms for each table structure you created.
c. Remove all transitive dependencies, write the relational schema, and draw the new dependency diagrams. Also identify the normal forms for each table structure you created.
d. Draw the Crow's Foot ERD.