2- Consider the following relation and given functional dependencies: STORE ITEM (SKU, PromotionID, Vendor, Style, Price) FD1: SKU, PromotionID à Vendor, Style, Price FD2: SKU à Vendor, Style (a) Identify the candidate keys and state its current normal form. (b) Normalize STORE_ITEM relation to the NEXT higher normal form. Explain clearly.

2- Consider the following relation and given functional dependencies: STORE ITEM (SKU, PromotionID, Vendor, Style, Price) FD1: SKU, PromotionID à Vendor, Style, Price FD2: SKU à Vendor, Style (a) Identify the candidate keys and state its current normal form. (b) Normalize STORE_ITEM relation to the NEXT higher normal form. Explain clearly.

Database System Concepts

7th Edition

ISBN:9780078022159

Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Chapter1: Introduction

Section: Chapter Questions

Problem 1PE

See similar textbooks

Similar questions

Define the connection between a relation's main key and the functional relationships between all of its attributes.
Develop an Entity Relationships Diagram (ERD) based on the relational schemas in the 3NF for the starting relational schema in un-normalized form presented below. UNF:Order(OrderID, OrderDate, CustID, CustName, CustPhone, CCNum, CCExpDate, CCBank, BnkContName, BnkContPhone, CustEmail, OrderIP, SiteRefFrom, ShipStreet, ShipCity, ShipSt, ShipZip, OrderLineNum, ItemID, ItemName, ItemDesc, ItemQtyOrdered,ItemListPrice, ItemSalePrice, ItemQtyShip, ShipCharge, Tax, TotalDue)
Write a relation algebra based on the following algebra: Book (BookID, Price, Year, Author, Subject) BorrowLog (BID, BookID, CustomerID, DateTime) Customer (CustomerID, CustomerName, Address, City) 1. List all tuples from books which their subjects are database 2. List all tuples from books published after 2010 which their subjects are database and the prices are at least 450 3. List information about author and subject from the relation, Book
What is the connection between a relation's primary key and the functional relationships between all of its attributes?
Primary key identifies a unique tuple of a relation, true or false?
Explain how functional dependencies may be used to indicate: • The entity sets student and teacher have a one-to-one relationship set.• Between entity setsstudent and teacher, there is a many-to-one connection set.
What is the link between the main key of a relation and the functional connections between all of its attributes?
Consider the following relation named Trip. Trip The functional dependencies are as follows: (TripID, TripName, StartLocation, State, Distance, MaxGrpSize, Type, SeasonNum, Season TripID, SeasonNum → TripID → A. SeasonNum →→ Season C. [TripName, StartLocation, State, Distance, MaxGrpSize, Type The tables that are in third normal form are: [TripName, StartLocation, State, Distance, MaxGrpSize, Type, Season Trip TripID, TripName, StartLocation, State, Distance, MaxGrpSize, Type) Season (Season Num, Season), TripSeason (TripID, SeasonNum) B. Trip (TripID, TripName, StartLocation, State, Distance, MaxGrpSize, Type) Season (SeasonNum, Season) Trip TripID, TripName, StartLocation, State, Distance, MaxGrpSize, Type) Season (TripID, SeasonNum, Season) D. None of the above
Explain the process of decomposing a relation to achieve higher normal forms and the potential trade-offs involved.
What is the link between a relation's main key and the functional dependencies among all of its attributes?
A hybrid merge-join strategy should be developed for the circumstance when both relations are not physically sorted, but both contain an index on the attributes that are being merged.
Given the following relation that stores details of employees and their projects: If the functional dependencies are consistent with the above relation, put TRUE. If they are not, put FALSE. 1.ProjectID ➡ EmployeeName 2.ProjectID ➡ EmployeeSalary 3.ProjectID , EmployeeName ➡ EmployeeSalary 4.EmployeeName ➡ EmployeeSalary 5.EmployeeSalary ➡ ProjectID 6.EmployeeSalary ➡ EmployeeName , ProjectID