the following relation with sample data. ns, Update Anomalies, and Normalization
ID: 3602873 • Letter: T
Question
the following relation with sample data. ns, Update Anomalies, and Normalization 121 ent of AIRPORT KLX TABLE AirlinelD AirlineName TerminalID NumberOfGates NumberOfDepartingFlights 11-Dec UA 11-DecNW 11-Dec AA 11-Dec DL 11-Dec JB 12-Dec UA 12-Dec DL Delta United Northwest A 20 20 20 15 34 Delta 8 et Blue United 20 15 15 20 6 29 20 12-Dec SWA Southwest C The AIRPORT KLX Table captures the data about dailu departing flights at the KLX Airport. ID and an Airline Name. E4.5b Using the AIRPORT KLX Table, describe an ex- ample that illustrates the deletion anomaly E4.5c Using the AIRPORT KLX Table, describe an ex- . Each airline operating at KLX airport has a unique Airline . Each terminal at KLX airport has a unique Terminal ID ample that illustrates the modification anomaly E4.5d Depict full key functional dependencies, partial and a fixed Number of Gates. functional dependencies (if any), and transitive func- tional dependencies (if any) in the AIRPORT KLX Table. . Each airline is permanently assigned to one (and only one) terminal at the KLX Airport . Each terminal at KLX Airport can have multiple airlines E4.5e Show the result of normalizing the AIRPORT KLX E4.5f Show the result of normalizing the AIRPORT KLX assigned to it. Departing Flights at KLX Airport for each airline. 4.5a Using the AIRPORT KLX Table, describe an ex- Table to 2NF . Each day (Date), this table records the Number of Table to 3NF. E4.5g Using the set of tables resulting from E4.5f, ample that illustrates the insertion anomaly. describe how the anomalies shown in E4.5a, E4.5b, and E4.5c are eliminated.Explanation / Answer
E4.5a)
Insert anomaly happens when certain attributes cannot be inserted into the database without the presence of other attributes in a table.
Example- Without having the information about the terminal like TerminalID, NumberOfGates etc., an airline information (AirlineID, AirlineName etc.) cannot be inserted.
E4.5b)
A Delete Anomaly occurs when certain attributes are lost on deletion of some other attributes.
Example- Suppose we wish to delete the information about an Airline with ID ‘SWA’. For deleting this particular airline the information related to the TerminalID ‘C’ will also be lost.
E4.5c)
An update anomaly occurs when one and more instances of duplicate data is updated but not all instances.
Example- Suppose we need to update the NumberOfGates of a particular TerminalID (‘A’), for this we need to update all instances of this TerminalID in the given database.
E4.5d)
Attributes are said to be fully functionally dependent when one attributes ‘X’ of a table uniquely identifies another attribute ‘Y’ (and not any subset of Y) of a table.
In the AIRPORT KLX table below are the full functional dependencies that exist-
AirlineID -> AirlineName
TerminalID -> NumberOfGates
No Partial and transitive dependency exist in the given table.
Related Questions
Navigate
Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.