{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

Design 5 is the best design of the available choices

Info iconThis preview shows pages 2–3. Sign up to view the full content.

View Full Document Right Arrow Icon
PURCHASE table, there should only be one theme. Design 5 is the best design of the available choices. F. PURCHASE(PurchaseID , Item, PurchasePrice, PurchaseDate) VENDOR(VendorID , Vendor, Phone) It improves design because using PurchaseID lets you find information better than looking for just a field name like Item, PurchasePrice, or PurchaseDate. It is unique and the others may not be. The same goes for VendorID in the VENDOR table. G. SALE (SaleID , SKUnumber, Item, InvoiceDate, Tax, Total, VendorID ) SALE_ITEM( SKUnumber , Item, Price)
Background image of page 2

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
PURCHASE(PurchaseID , SKUnumber , Item, PurchasePrice, PurchaseDate, VendorID ) VENDOR(VendorID , Vendor, Phone) The vendor can be a business like Walmart with different locations. This vendor makes a purchase, which is why the VendorID is a foreign key in PURCHASE. The item bought has a sku number, which is why we added SkuNumber as a primary key in purchase and foreign keys in both sale and sale_item. The vendor then sells the item purchased previously, which is why VendorID is shown as a foreign key in the SALE table.
Background image of page 3
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}