Considering the un-normalized relational table PROJECT below: PROJECT (ProjectTitle, EmpeName, ManagerName, Location, HoursWork, ManagerPhone) The attributes of PROJECT table satisfy the following properties: Each project has many employees, Each employee may involve in one or more projects, Projects are managed by managers; there are many managers in the company, hence a project may be assigned to any one of the managers, but each manager manages only one project. Each project is located in a specific location, The number of hours an employee works at each project is determined by a project title and the name of an employee. Each manager has a telephone number. Normalize the relational table PROJECT into a minimal number of relational tables in BCNF. Use the functional dependencies to prove that each one of the relational tables obtained from the decomposition of the original table is in BCNF.

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…

Please follow this ER diagram, give a description, and make a schema diagram from it. Also, make database (constraint tables) & intent some sample data. Lastly, run some SQL functions code.   Please don't copy from anywhere. I need it for my project.

The value range of an attribute must be large enough for the index to be relevant. Except for this one use case, an index is never helpful.

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.

Topic: Database Design and Entity Relationship Diagrams Please convert the following diagram to Crow's Foot notation.

Review the SaleItem relation below where ItemNumber plus OrderNumber is the primary key. What type of primary key does this relation have? SALEITEM (ItemNumber, OrderNumber, Quantity, Price)   Group of answer choices Composite primary key Surrogate primary key Transitive primary key Alternate primary key

q1

PLz help with the following: Translate your ER diagram into a relational schema in the form of SQL DDLs. Choose appropriate data types for each attribute and include primary key and foreign key constraints, Check and Not Null constraints.

ERD for Sales Order Step 1. Draw an ER diagram for the story below. Use the ERD tool only. Draw Relations in Oracle notation. Please read the story carefully. Use the mentioned Entities ONLY. The company sells various Products to Customers. The Sales Agent books an Order. A new order is created for each Product. While booking an Order, Agent records Order Date, Product, Customer, Product Quantity, and Sales Agent. Product has Description and UnitPrice. Each Agent reports to a Manager. A Manger has a Nameand Commission Percent. NOTE: Total Amount is a calculation, doesn't belong to Order Step 2. Add Attributes to Sales Order ERD based on Rules of Normalization.