Assume that alter table statements will NOT be used in this question. Assume that all tables with all constraints were created based on the company schema. In order to drop tables successfully, the project table must be dropped before the department table. True False

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…

Instructions: In this assignment, you will convert an Entity-Relationship diagram into a set of related tables. Given the following ERD, write the table definitions for the entities displayed below.  You do not have to indicate data types nor “not null” constraints in this lab.  Use the format TableName ( attribute, attribute…attribute).  Designate primary keys with an underline and foreign keys with a broken underline.  To illustrate, the Regions and Countries table definitions have been created for you below the diagram.  Type your answers in this document and upload it to the appropriate Blackboard assignment link by Monday at 11:59 p.m. ET of this module/week. Note that you should read the “Table Conversions Explained” document in your Reading & Study folder.  I created it to help you better understand how ERDs will ultimately be transformed into real tables.   ERD for the Hourglass timekeeping database

Should NOT INCORRECT DB REMEMBER. I NEED GENUINE DB NOT ILLOGICAL.

StayWell also rents out properties on a weekly basis to students attending summer school in the Seattle area. Design a database to meet the following requirements, using the shorthand representation and a diagram of your choice. For each student renter, list his or her number, first name, middle initial, last name, address, city, state, postal code, telephone number, and e-mail address. For each property, list the office number, property address, city, state, postal code, square footage, number of bedrooms, number of floors, maximum number of persons that can sleep in the unit, and the base weekly rate. For each rental agreement, list the renter number, first name, middle initial, last name, address, city, state, postal code, telephone number, start date of the rental, end date of the rental, and the weekly rental amount. The rental period is one or more weeks.

Your task is to break this up into a list of "normalized" tables that you describe using the text-based "relational notation".  You will need to break this example into as many separate tables as you feel is appropriate to remove all modification anomalies. Please submit your relational notations in an ordinary word document along with the sample data in a "grid". I'm expecting to see both PK and FK notations in your submission. Note: I'm not asking for a database... I'm asking for a list of tables in relational notation plus the sample data in rows/columns.   Part One: Use text-based relational notation to describe each table/field Note: I am not yet requiring you to solve the "multi-column" problem Show PK and FK (use Microsoft Word's underline and italics tools) Part Two:  Create a "grid" for each table with the all of the rows/columns of data for that table after normalization (to include PKs/FKs) Make sure you don't have any duplicate rows in your "grid" Note: You can just do…

Question 3: Create the DDL statements to create the tables described in your modified ER diagram in question 2: DDL Statement: CREATE TABLE School ( school_code integer Primary Key(10), location varchar(25), name varchar(10) ); CREATE TABLE Professors ( staff_id integer(10), name varchar(20), school varchar(30) ); CREATE TABLE Course ( subject_code varchar(10), school varchar(30), name varchar(10) ); CREATE TABLE Subject ( subject_code(10), school varchar(30), name varchar(10) ); CREATE TABLE Student ( student_id number(10), name varchar(10), address varchar(30), phone number(10) ); Table Description desc table School; Select * from School; Name                       Null              Type school_code Not null integer location Not null varchar(25) name Not null varchar(10)   desc table Professor; Select * from Professor; Name               Null              Type staff_id Not null number(10) name   varchar(20) school   varchar(30)   desc table Course; Select * from…