Consider the following relations for a Guest Room reservation application database. Room (room_id, room_availability, booking date. Cust_ id. booking details) Customer(Cust id. CNIC, E name. L name. Address, Contact number. MembershipNo.) Assume that each Hotel of a city has different mumber of rooms where each room can be booked by any customer at any time subject to its availability. If we apply a natural join on the relations Room and Customer in this database, what does the resulting relation schema look like? Explain the result of this operation. Show the Functional Dependencies in this resulting relation. Is it in 2NF? Is it in 3NF? Why or why not? (State assumptions, if you make any.)

Consider the following relations for a Guest Room reservation application database. Room (room_id, room_availability, booking date. Cust_ id. booking details) Customer(Cust id. CNIC, E name. L name. Address, Contact number. MembershipNo.) Assume that each Hotel of a city has different mumber of rooms where each room can be booked by any customer at any time subject to its availability. If we apply a natural join on the relations Room and Customer in this database, what does the resulting relation schema look like? Explain the result of this operation. Show the Functional Dependencies in this resulting relation. Is it in 2NF? Is it in 3NF? Why or why not? (State assumptions, if you make any.)

Database System Concepts

7th Edition

ISBN:9780078022159

Author:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Publisher:Abraham Silberschatz Professor, Henry F. Korth, S. Sudarshan

Chapter1: Introduction

Section: Chapter Questions

Problem 1PE

See similar textbooks

Similar questions

The table STUDENT has the attributes STUDENT_ID, NAME, SCHOOL_ID, and ADDR. The table SCHOOL has the attributes SCHOOL_ID, NAME, and STATE_CODE. Assume that there is a 1:N relation between SCHOOL and STUDENT. Which of the following creates a table that shows the STUDENT attributes and the corresponding SCHOOL attributes? a. SELECT * SCHOOL_ID FROM STUDENT JOIN SCHOOL b. SELECT * SCHOOL_ID FROM STUDENT JOIN SCHOOL USING(SCHOOL_ID) c. SELECT * SCHOOL_ID FROM STUDENT NATURAL JOIN SCHOOL d. SELECT * SCHOOL_ID FROM STUDENT, SCHOOL WHERE SCHOOL_ID = SCHOOL_ID
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…
The Driver Relationship team wants to ensure that the all driving license IDs in the active drivers table have the length of 7. Alter the ACTIVE_DRIVERS table created in Chapter 8, Activity 1 to check the length of the DRIVER_DRIVING_LICENSE_ID.
For the attached database, use relational algebra and find the loan_numbers only for the loans with the smallest loan amounts. (Using renaming and set difference). Which database relation(s) could be joined with the result of the query of the previous inquiry to find the Id, name, city, and loan amount for the borrowers having the smallest loan amount?
Suppose that A and B are two sets of entities connected by a relation R that has multiple one-to-one occurrences (see Figure 1). Think about a scenario in which R's generated connection is coupled with A's. SQL allows null values for attributes that are a part of a foreign key constraint. Give an example of how non-null constraints may be used in SQL to place a restriction on how much A can be involved in R.
Run the problem using Relational Algebra, below the problem I added the needed table. Use self join find the answer (4) Find the name (fname,lname) of the direct supervisor of “Mary Smith”. (“Mary Smith” is an employee). group: emplyeeemployee = {fname, lname, ssn,superssn, departnumber'Mary', 'Smith',111, 222, 11'Green', 'Marjorie',333, 222, 12'Gren', 'Cheryl',222, 777, 14}