ATTRIBUTE SAMPLE VALUE SAMPLE VALUE SAMPLE VALUE SAMPLE VALUE SAMPLE VALUE NAME | 211347 AA-E3422QW 211348 AA-E3422QW INV_NUM 211347 211347 211349 PROD_NUM QD-300932X RU-995748G GH-778345P SALE_DATE 15-Jan-2018 15-Jan-2018 15-Jan-2018 15-Jan-2018 16-Jan-2018 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 1 2 1 PROD_PRICE $49.95 $3.45 $39.99 $49.95 $87.75
Using the INVOICE table structure shown in Table P6.3, do the following:
TABLE P6.3
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.
Note
You can assume that any given product is supplied by a single vendor, but a vendor
can supply many products. Therefore, it is proper to conclude that the following
dependency exists:
PROD_NUM → PROD_LABEL, PROD_PRICE, VEND_CODE, VEND_NAME
(Hint: Your actions should produce three dependency diagrams.)
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.
Trending now
This is a popular solution!
Step by step
Solved in 4 steps with 3 images
