Normalize the provided flat file into three relations: Member, Transaction, and Operation.

Hey nkemdivo, good to see you again. Here's the solution to your database normalization problem. Task A1: Database (20 Marks) The problem asks to normalize a flat file into three relations: 1. Member(MID, MName, MAdd) 2. Transaction(TID, TType, Amount) 3. Operation(MID, TID, ODate) 1. Develop the Member table: The Member table should contain unique MID, MName, and MAdd entries from the original Table 1. Step 1: Identify unique MID, MName, and MAdd combinations from Table 1. • M10, Mbong, Buea • L05, Lyonga, Bamenda • O20, Otia, Wum • O15, Omar, Garoua • S04, Susan, Douala • L12, Linus, Bertoua • G11, Gertrude, Yaounde • T07, Tita, Maroua Step 2: Construct the Member table with these unique entries. ` Member +-----+--------+----------+ | MID | MName | MAdd | +-----+--------+----------+ | M10 | Mbong | Buea | | L05 | Lyonga | Bamenda | | O20 | Otia | Wum | | O15 | Omar | Garoua | | S04 | Susan | Douala | | L12 | Linus | Bertoua | | G11 | Gertrude| Yaounde | | T07 | Tita | Maroua | +-----+--------+----------+ ` The Member table is: ` Member(MID, MName, MAdd) MID | MName | MAdd ----|---------|---------- M10 | Mbong | Buea L05 | Lyonga | Bamenda O20 | Otia | Wum O15 | Omar | Garoua S04 | Susan | Douala L12 | Linus | Bertoua G11 | Gertrude| Yaounde T07 | Tita | Maroua ` This table is derived by selecting distinct combinations of MID, MName, and MAdd from the original Table 1. 2. Give the reason why the table above is not normalized. The original Table 1 is not normalized because it contains redundant data and update anomalies. Specifically: • Redundancy: Member details (MName, MAdd) are repeated for each transaction by the same member. For example, "Mbong, Buea" appears multiple times. • Update Anomalies: If a member's address changes, multiple rows would need to be updated. If one row is missed, data inconsistency occurs. • Insertion Anomalies: A new member cannot be added without a transaction. • Deletion Anomalies: Deleting a member's last transaction would also delete the member's details. These issues indicate that the table is not in at least First Normal Form (1NF) due to repeating groups of non-key attributes, and certainly not in higher normal forms like 2NF or 3NF due to partial and transitive dependencies. 3. State the key for each of the tables. • For Member(MID, MName, MAdd): The key is MID. • For Transaction(TID, TType, Amount): The key is TID. • For Operation(MID, TID, ODate): The key is a composite key of (MID, TID). Drop the next question 📸