Please convert following figure into a relational schema. In each table, the primary key and foreign keys (arrows) must be identified. Code BANK Name Addr BRANCHES ACCTS Acct no N N Balance ACCOUNT Type BANK BRANCH Addr LOANS Loan no N Branch no LOAN Amount Type

Please convert following figure into a relational schema. In each table, the primary key and foreign keys (arrows) must be identified. Code BANK Name Addr BRANCHES ACCTS Acct no N N Balance ACCOUNT Type BANK BRANCH Addr LOANS Loan no N Branch no LOAN Amount Type

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 relational schema shown below is part of a hospital database. The primary keys are highlighted in bold. Patient (patientNo, patName, patAddr, DOB)Ward (wardNo, wardName, wardType, noOfBeds)Contains (patientNo, wardNo, admissionDate)Drug (drugNo, drugName, costPerUnit)Prescribed (patientNo, drugNo, unitsPerDay, startDate, finishDate) Formulate the following SQL statements: a) Find the names of all the patients being prescribed ‘Morphine’.b) What is the total cost of Morphine supplied to a patient called ‘John Smith’?c) For each ward that admitted more than 10 patients today, list the ward number, ward type and number of beds in each ward.
ER Mapping : Convert the ER diagram into a relational database schema. For each relation, specify the primary keys and the foreign key(s) if any (50 pts) Upload you Relational Diagram here BANK BRANCHES BANK-BRANCH Code Name Addr Addr BranchNo АССTS LOANS N AcctNo Balance LoanNo Amount ACCOUNT Туре LOAN Type M M A-C L-C N Name N. SSN Phone CUSTOMER Addr
The relational schema shown below is part of a hospital database. The primary and foreign keys are highlighted in bold. Patient (patientNo, patName, patAddr, DOB)Ward (wardNo, wardName, wardType, noOfBeds)Admission (patientNo, wardNo, admissionDate)Drug (drugNo, drugName, costPerUnit)Prescribed (patientNo, drugNo, unitsPerDay, startDate, finishDate) Write SQL queries based on the hospital database given above: 1. Create the above tables together with its constraints. 2. Insert some data into the tables to check that the tables created are correct. No limit on how many rows you want to add. Insert Syntax:insert into table_namevalues (col1_value, col2_value, etc.); 3. List all the patients’ details, alphabetically by name. IF YOU WANT SOME CHALLENGE4. List all the patients admitted today. (Join between Patient and Admission table)
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…
Database Schema The schema for the Ch07_FACT database is shown below and should be used to answer the next several problems. Click this image to view it in its own tab. FIGURE P7.56 THE CH07_FACT ERD CHECKOUT PATRON PK Check Num PK Pat ID FK1 Book_Num FK2 Pat_ID Check_Out_Date Check_Due_Date Check_In_Date >0-----H- Pat_FName Pat LName Pat_Type BOOK AUTHOR PK Book_Num PK Au ID Book_Title Book_Year Book_Cost Book_Subject FK1 Pat_ID Au_FName Au_LName Au_BirthYear WRITES PK,FK1 Book Num PK,FK2 Au ID The CIS Department at Tiny College maintains the Free Access to Current Technology (FACT) library of e-books. FACT is a collection of current technology e-books for use by faculty and students. Agreements with the publishers allow patrons to electronically check out a book,
DailyCases * Day PCRTests 9 TestNo Patientid TodalTestCount DateofTest PositiveTestCount Result NegativeTestCount Tester DateofResult Department TotalCases * Dey DepartmentName TotalTestCount TotaPositiveCount Patient * Patientid Employee * Empoyeeld FirstName LastName Title IdentityNumber FirstName RegisteredDate LastName BloodGroup Department CurrentStatus StartDate HesCode Figure 1 According the database design given in Figure 1; Write a SQL statement to display PCR test results as below (Figure 2). First Name of Patient Last Name of Patient Date of Test Ttle of Tester Name of Tester Date of Result Resut DİŞÇİ Prof Dr. Eren Bakız 2021-01-20 00:00:00.000 Pending VOLKAN 2021-12-01 YILDIZ MUHAMMET EMİN TUNÇ OZALP 2 SAFA 2021-12-01 Dr. Bartu Olay 2021-01-21 00:00.00.000 Pendng 3 2021-12-01 Prof Dr. Eren Bakız 2021-01-18 00 00-00.000 Pending 2021-01-12 Bartu Olay Bartu Olay HILAL Dr. 2021-01-18 00:00.00.000 Pendng BURAK AŞRAK 2021-01-12 Dr. 2021-01-20 00:00:00.000 Positive 6 ALI TAHA…
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…
Write the DDL statements for declaring the Library relational database schema listed below. Specify the kay (Primary and Foreign where applicable). BOOK Book id Title Publisher name BOOK AUTHORS Bock id Author name PUBLISHER Name Address Phone BOOK COPIES Book d Branch id No ef_oopies BOOK LOANS Book id Branch id Card no Dute out Due date LIBRARY BRANCH Branch id Branch name Addresa BORROWER Card no Name Addre Phone
A relation cannot have: Multi-values attributes Several super-keys Composite attributes Attributes with atomic values
Consider the following ER diagram: storcid address description value Displays Store Memorabilia The above diagram represents information pertaining to stores and the memorabilia that is displayed within the stores. a) Write the SQL statements to create 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).
The relational database below contains two related tables - “Supplier” and “Product”: “Product” table: Primary key = Prod-code, Foreign key = Supp-code Prod-code Prod -name Prod -desript Prod -stocktype Prod -stocklevel Prod -expireDate Supp-code 10010 aaa qwert 615 123445677 2017-11-14 501 10011 bbb asdfgg 615 234567899 2017-11-16 501 10012 ccc zxxcvv 234 345678900 2017-11-13 502 10013 eee ytuytu 234 454577777 2017-10-13 503 10014 jjj werewr 231 436436885 2017-10-23 503 10015 sdg rtyrtyry 275 676446322 2017-10-30 504 10016 ewt erterter 789 232317879 2017-12-30 501 “Supplier” table: Primary key = Supp -code, No Foreign key Supp -code Supp -lname Supp -fname Supp -Initial Supp -areacode Supp -phone 501 xxx qwert F 615 123445678 502 yyy asdfgg B 615 234567890 503 zzz zxxcvv X 234 345678901…