Convert this table to 1* nomal form. Identify the primary key(s) in the table. Draw as-is dependency diagram and identify types of dependencies. Is this table 3rd normal form? If not, convert it to 3rd normal form. Student Birth Course ID Course Prerequisite ID Student Student First Course ID Name Date Grade 16830 Williams 1/31/2000 IS 350 A IS 300 16830 Williams 1/31/2000 IS 465 B IS300, IS 350 54329 Baker 2/29/1998 IS 350 A IS 300 54329 Baker 2/29/1998 IS 465 A IS300, IS 350

Implement a new independent entity phone in the Sakila database. Attributes and relationships are shown in the following diagram:   The diagram uses Sakila naming conventions. Follow the Sakila conventions for your table and column names: All lower case Underscore separator between root and suffix Foreign keys have the same name as referenced primary key Write CREATE TABLE and ALTER TABLE statements that: Implement the entity as a new phone table. Implement the has relationships as foreign keys in the Sakila customer, staff, and store tables. Remove the existing phone column from the Sakila address table. Step 2 requires adding a foreign key constraint to an existing table. Ex: ALTER TABLE customer ADD FOREIGN KEY (phone_id) REFERENCES phone(phone_id) ON DELETE SET NULL ON UPDATE CASCADE; Specify data types as follows: phone_id, phone_number, and country_code have data type INT. phone_type has date type VARCHAR(12) and contains strings like 'Home', 'Mobile', and 'Other'. Apply…

Implement a new independent entity phone in the Sakila database. Attributes and relationships are shown in the following diagram:   The diagram uses Sakila naming conventions. Follow the Sakila conventions for your table and column names: All lower case Underscore separator between root and suffix Foreign keys have the same name as referenced primary key Write CREATE TABLE and ALTER TABLE statements that: Implement the entity as a new phone table. Implement the has relationships as foreign keys in the Sakila customer, staff, and store tables. Remove the existing phone column from the Sakila address table. Step 2 requires adding a foreign key constraint to an existing table. Ex: ALTER TABLE customer ADD FOREIGN KEY (phone_id) REFERENCES phone(phone_id) ON DELETE SET NULL ON UPDATE CASCADE; Specify data types as follows: phone_id, phone_number, and country_code have data type INT. phone_type has date type VARCHAR(12) and contains strings like 'Home', 'Mobile', and 'Other'. Apply…

Convert the Entity Relationship Diagram in to Q1. relational database by using MS Access (Note: Students has to create tables in the MS Access by giving appropriate Primary key and Foreign key relationships) Customer Order OrderDetail OrderID OrderDetaillD CustomerID OrderID (FK) Name Mail CustomerID (FK) OrderDate TotalPrice ProductID (FK) ZipCode Address Telephone Amount Price Product ProductID Name Kind Price

Implement a new independent entity phone in the Sakila database. Attributes and relationships are shown in the diagram below   The diagram uses Sakila naming conventions. Follow the Sakila conventions for your table and column names: All lower case Underscore separator between root and suffix Foreign keys have the same name as referenced primary key Write CREATE TABLE and ALTER TABLE statements that: Implement the entity as a new phone table. Implement the has relationships as foreign keys in the Sakila customer, staff, and store tables. Remove the existing phone column from the Sakila address table. Step 2 requires adding a foreign key constraint to an existing table. Ex: ALTER TABLE customer ADD FOREIGN KEY (phone_id) REFERENCES phone(phone_id) ON DELETE SET NULL ON UPDATE CASCADE; Specify data types as follows: phone_id, phone_number, and country_code have data type INT. phone_type has date type VARCHAR(12) and contains strings like 'Home', 'Mobile', and 'Other'. Apply these…

Write the SQL statements to create all of the necessary tables to represent the above diagram, representing as many constraints as possible. Note: you do not need to worry about specifying types for the fields, but you do need to provide suitable foreign key option(s). When playing a game, the home team name should be stored in attribute htname and the away team name should be stored in atname.

1. Given the followving relation that stores details about students' activities: ActivityFee AmountPaid 65.00 StudentID StudentName Activity Golf 100 Jones 65.00 100 Jones Skiing Skiing 200.00 0.00 200 Davis 200.00 0.00 200 Davis Swimming Skiing Swimming 50.00 50.00 50.00 300 Garrett 200.00 100.00 300 Garrett 50.00 400 Jones Golf 65.00 65.00 400 Swimming 50.00 Jones 50.00 If the functional dependencies are consistent with the above relation, put TRUE. If they are not, put FALSE. StudentID → StudentName StudentID , StudentName → Activity Activity > ActivityFee Activity → StudentID StudentID → Activity StudentID → AmountPaid ||

Consider a Student table containing StudentNum, StudentName, StudentMajor, AdvisorNum, AdvisorName,AdvisorOfficeNum, AdvisorPhone, NumCredits, and Category (freshman, sophomore, and so on). List thefunctional dependencies that exist, along with the assumptions that would support those dependencies

Create a class diagram for the BITS Corporation database, as shown in Figure 1-5 in Chapter 1 (see attached image). If you need to make any assumptions when preparing the class diagram, document those assumptions.

Indicate dependences and their type.