Database Systems: Design, Implementation, & Management
12th Edition
ISBN: 9781305627482
Author: Carlos Coronel, Steven Morris
Publisher: Cengage Learning
expand_more
expand_more
format_list_bulleted
Expert Solution & Answer
Chapter 2, Problem 14RQ
Explanation of Solution
Relational Diagram:
- A relational diagram refers to a visual representation of the relational
database ’s entities, the relationships between those entities, and the attributes within those entities. - Therefore, it makes it easy to understand what the entities represent, what types of relationships exist and how these relationships are implemented.
Example of Relational Diagram:
- The relational diagram given below shows the connecting fields that is, “AGENT_CODE” through 1:M relationship type.
- To illustrate simple relational diagrams, use MS Access, Database tools, and “relationships” options on the main Access menu...
Expert Solution & Answer
Trending nowThis is a popular solution!
Students have asked these similar questions
how do you translate an Entity Relational Diagram to a Relational Diagram?
Create a diagram for a database with at least 5 tables. This should show your table names and column names. Show the relationships between
the tables. Write a statement explaining your database design (why did you use the tables that you did).
Create a database in Access based on your diagram. Include all tables in your diagram. Tables should each have a minimum of 5 rows.
Create 5 SQL statements using your database. At least 2 of these should be manipulation statements (insert, update, etc). The others should
be select statements. Explain what your sql statements do and how they would be useful to your database.
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…
Chapter 2 Solutions
Database Systems: Design, Implementation, & Management
Ch. 2 - Prob. 1RQCh. 2 - What is a business rule, and what is its purpose...Ch. 2 - How do you translate business rules into data...Ch. 2 - Prob. 4RQCh. 2 - Explain how the entity relationship (ER) model...Ch. 2 - Prob. 6RQCh. 2 - Prob. 7RQCh. 2 - Prob. 8RQCh. 2 - Prob. 9RQCh. 2 - Prob. 10RQ
Ch. 2 - What is a relationship, and what three types of...Ch. 2 - Give an example of each of the three types of...Ch. 2 - What is a table, and what role does it play in the...Ch. 2 - Prob. 14RQCh. 2 - Prob. 15RQCh. 2 - Prob. 16RQCh. 2 - Prob. 17RQCh. 2 - Prob. 18RQCh. 2 - Prob. 19RQCh. 2 - Prob. 20RQCh. 2 - Prob. 21RQCh. 2 - Prob. 22RQCh. 2 - Prob. 23RQCh. 2 - Prob. 1PCh. 2 - Prob. 2PCh. 2 - Prob. 3PCh. 2 - Prob. 4PCh. 2 - Prob. 5PCh. 2 - Using Figure P2.6 as your guide, work Problems 68....Ch. 2 - Prob. 7PCh. 2 - Prob. 8PCh. 2 - Typically, a hospital patient receives medications...Ch. 2 - Prob. 10PCh. 2 - Prob. 11PCh. 2 - Prob. 12PCh. 2 - Prob. 13PCh. 2 - Prob. 14PCh. 2 - Prob. 15PCh. 2 - Prob. 16PCh. 2 - Prob. 17P
Knowledge Booster
Similar questions
- The ______________ model is a simple but highly useful way to organize data into collections of two-dimensional tables called relations.arrow_forwardImplement 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…arrow_forwardImplement 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…arrow_forward
- An actual SQL database example should be provided.arrow_forwardWhen using subtype associations, it's vital to talk about the different database table alternatives. Choose a design and talk about the issues that will develop as a result of it. Computer sciencearrow_forwardConvert 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 Pricearrow_forward
- Convert the Entity Relationship Diagram in to 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) QI. Customer Order OrderDetail CustomeriD OrderiD OrderiD (FK) OrderDetaillD Name Mail ZipCode Address Telephone CustomeriD (FK) OrderDate TotalPrice ProductiD (FK) Amount Price Product ProductiD Name Kind Pricearrow_forwardWhy do you think entity relationship (ER) diagrams are important in database design?arrow_forwardIndicate the changes (using the shorthand representation) that you would need to make to the original KimTay Pet Supplies database design to support the following requirements. There is no relationship between customers and sales reps. When a customer places an order, any sales rep can process the order and create the invoice. On the invoice, you need to identify both the customer placing the order and the sales rep responsible for the invoice. Draw an E-R diagram for the new design.arrow_forward
- Indicate the changes (using the shorthand representation) that you would need to make to the original KimTay Pet Supplies database design to support the following requirements. There is no relationship between customers and sales reps. When a customer places an order, any sales rep can process the order and create the invoice. On the invoice, you need to identify both the customer placing the order and the sales rep responsible for the invoice. Draw an E-R diagram for the new design.arrow_forwardExplain the significance of entity relationship diagrams in relational database design and why you think they are useful.arrow_forward97. The column header of table in relational model terminology is classified as a. attribute b. table starter c. table ender d. entity domainarrow_forward
arrow_back_ios
SEE MORE QUESTIONS
arrow_forward_ios
Recommended textbooks for you
Principles of Information Systems (MindTap Course...Computer ScienceISBN:9781285867168Author:Ralph Stair, George ReynoldsPublisher:Cengage Learning
Principles of Information Systems (MindTap Course...Computer ScienceISBN:9781305971776Author:Ralph Stair, George ReynoldsPublisher:Cengage Learning
Principles of Information Systems (MindTap Course...
Computer Science
ISBN:9781285867168
Author:Ralph Stair, George Reynolds
Publisher:Cengage Learning
Principles of Information Systems (MindTap Course...
Computer Science
ISBN:9781305971776
Author:Ralph Stair, George Reynolds
Publisher:Cengage Learning