Question 2Consider the following relation:Computer Repair(Comp ID, Engineer ID, Date Assigned, Customer_name, Customer_phone,Engineer_Name, Engineer_phone, Date_Repaired, Issue, Priority_Level, Service_Charge,Commission_Percentage, Total_Repairs)The primary key of the relation is underlinedThe relation has the following additional functional dependencies:FD1: Engineer_ID →→ Engineer_Name, Total_Repairs, Commission_Percentage,Engineer_phoneFD2: Comp_ID, Date_Assigned → Issue, Priority_Level, Service_ChargeFD3: Comp_ID Customer_name, Customer_phoneFD4: Priority Level Service ChargeFD5: Total RepairsCommission_Percentagei. Explain if this is in 1NF or not. If not, apply normalization to decompose it to 1NF.ii. Explain if this is in 2NF or not. If not, apply normalization to decompose it to 2NF.iii. Explain if this is in 3NF or not. If not, apply normalization to decompose it to 3NF

Normalization is an essential step in database architecture that guarantees data integrity,…

Question 2 Consider the following relation: Computer Repair(Comp ID, Engineer ID, Date Assigned, Customer_name, Customer_phone Engineer_Name, Engineer_phone, Date_Repaired, Issue, Priority_Level, Service_Charge Commission_Percentage, Total_Repairs) The primary key of the relation is underlined The relation has the following additional functional dependencies: FD1: Engineer_ID →→ Engineer_Name, Total_Repairs, Commission_Percentage, Engineer_phone

Question 2 Consider the following relation: Computer Repair(Comp ID, Engineer ID, Date Assigned, Customer_name, Customer_phone Engineer_Name, Engineer_phone, Date_Repaired, Issue, Priority_Level, Service_Charge Commission_Percentage, Total_Repairs) The primary key of the relation is underlined The relation has the following additional functional dependencies: FD1: Engineer_ID →→ Engineer_Name, Total_Repairs, Commission_Percentage, Engineer_phone

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

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
Map the EER diagram to a relational schema and transform the relation into 3NF
Transform ERD into Relation
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 of the customer names who have borrowed the book written by James Clear 2. List the subject of the books that were borrowed on the date, 2021-10-07, but not on 2021-10-01 3. List the subject of the books that were borrowed by the customers who are in Bangkok.
Explain how functional dependencies can be used to indicate the following: A one-to-one relationship set exists between entity sets student and Instructor. A many-to-one relationship set exists between entity sets student and instructor.
Computer Science Design an Extended Entity Relationship Model with appropriate cardinality and appropriate entity names which can later be used in SQL to test queries and validate entity relations for the following case. The car hire company caters for both corporate and individual customer hire. Corporate customers are allocated a type, gold, silver or bronze based on the frequency of hire arranged in the contract. Vehicles on corporate and/or individual hire can be collected at any centre and dropped at any centre (with no surcharge for a different centre). Hire charges are based on vehicle classifications (e.g. Luxury Saloon, Basic Hatchback ....) Each classification will include a variety of models (e.g. Ford Fiesta 1.1, Fiat Panda ....are in the ‘Basic Hatchback’ classification). Charges for classifications are by the day. A customer collecting a car at a particular centre will be charged according to the charges for that centre.
Swing Jazz Club ERD Problem Follow the Simple Procedure for ERD diagramming to design an ERD using the following user provided information. Remember the ERD will eventually turn into the design for a database from a top down view. Make sure you resolve any many to many conflicts. Label an identifier or primary key and all pertinent attributes given. If an attribute is not readily apparent from the user information, then make one up that makes sense for the particular entity. Therefore, all entities should end up with at least an identifier and another attribute that makes sense. You may use any of the approaches shown by the book, though the ER-Model and Crow’s foot are the most common. Make sure you show entities, relationships, cardinality, and optionality. Swing Jazz Club The Swing Jazz Club teaches swing and jazz dancing and offers both private and group lessons. Swing Jazz charges $60 dollars per hour for a private lesson and $10 dollars per hour for a group lesson.…
Map the EER diagram to a relational schema and transform the relation into 3NF
1. Convert the conceptual ERD to Logical ERD 2. Derive the relation schema. Figure 6: AUTHOR PUBLICATION pub_ID (pk) publish_date author_num (pk) Li author_Iname author fname author phone works (MANDATORY, or ORGANIZATION BOOK ARTICLE book title book category book publisher article title keyword org ID (pk) org name org address published_in LI JOURNAL journal ID (pk) journal name year publisher volume SUBJECT LI subject_name (pk) category
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