Concept explainers
a.
Normalization:
The process used to minimize data redundancy and dependency in a relational
Second normal form (2NF):
- The value of all non-primary key attributes should be dependent on the primary key attribute.
- If any attribute is depending on the partial primary key then it should determine the other attributes for an instance of the entity.
- The partial dependencies should be removed from the data model.
Third normal form (3NF):
- The value of any non-primary key attributes will not depend on any other non-primary key attributes.
- If any non-primary key attributes depend on any other non-primary key attribute then it should be moved or deleted.
- It is termed as transitive dependency.
Partial dependency:
A partial dependency exists at that time of an attributes depends only a part of primary key. This dependency is related with 1st normal form.
Transitive dependency:
A transitive dependency exists at that time of an attributes depends on another attribute which is not part of primary key.
Functional dependency:
An association between two attributes or two set of attributes in a same relational database table, which is having some constraints is known as functional dependency.
- In a table one attribute is functionally dependent on another attribute to take one value.
a.
Explanation of Solution
Construct the dependency diagram with all partial and transitive dependencies:
The relational schema for given INVOICE table is given below:
Invoice(INV_NUM, PROD_NUM, SALE_DATE, PROD_LABEL, VEND_CODE, VEND_NAME, QUANT_SOLD, PROD_PRICE)
- Here, “INV_NUM” and “PROD_NUM” indicates the primary key.
The representation of dependency diagram with all partial and transitive dependencies is shown below:
Explanation:
In the above dependency diagram,
- The partial dependencies are,
INV_NUM -> (SALE_DATE)
PROD_NUM -> (PROD_LABEL, VEND_CODE, VEND_NAME, PROD_PRICE)
- The transitive dependency is,
VEND_CODE -> (VEND_NAME)
b.
Normalization:
The process used to minimize data redundancy and dependency in a relational database is known as normalization. The database table is divided into two or more tables and defines the relationship between those tables.
Second normal form (2NF):
- The value of all non-primary key attributes should be dependent on the primary key attribute.
- If any attribute is depending on the partial primary key then it should determine the other attributes for an instance of the entity.
- The partial dependencies should be removed from the data model.
Third normal form (3NF):
- The value of any non-primary key attributes will not depend on any other non-primary key attributes.
- If any non-primary key attributes depend on any other non-primary key attribute then it should be moved or deleted.
- It is termed as transitive dependency.
Partial dependency:
A partial dependency exists at that time of an attributes depends only a part of primary key. This dependency is related with 1st normal form.
Transitive dependency:
A transitive dependency exists at that time of an attributes depends on another attribute which is not part of primary key.
Functional dependency:
An association between two attributes or two set of attributes in a same relational database table, which is having some constraints is known as functional dependency.
- In a table one attribute is functionally dependent on another attribute to take one value.
b.
Explanation of Solution
Construct the dependency diagram by removing all partial dependencies:
The new dependency diagram is represented by removing all partial dependencies in INVOICE table.
First table:
The relational schema for first table is given below:
3NF(INV_NUM, PROD_NUM, SALE_DATE, QUANT_SOLD)
- Here, “INV_NUM” and “PROD_NUM” indicates the primary keys.
- The relation is in third normal form (3NF), since there is no transitive dependency and no repeated attributes.
The representation of dependency diagram removes all partial dependencies in first table are shown below:
Second table:
The relational schema for second table is given below:
3NF(INV_NUM, SALE_DATE)
- Here, “INV_NUM” indicates the primary key.
- The relation is in third normal form (3NF), since there is no transitive dependency and no repeated attributes.
The representation of dependency diagram removes all partial dependencies in second table are shown below:
Third table:
The relational schema for third table is given below:
2NF(PROD_NUM, PROD_LABEL, VEND_CODE, VEND_NAME, PROD_PRICE)
- Here, “PROD_NUM” indicates the primary key.
- The relation is in third normal form (2NF), since there is transitive dependency in table.
The representation of dependency diagram removes all partial dependencies in third table are shown below:
c.
Normalization:
The process used to minimize data redundancy and dependency in a relational database is known as normalization. The database table is divided into two or more tables and defines the relationship between those tables.
Second normal form (2NF):
- The value of all non-primary key attributes should be dependent on the primary key attribute.
- If any attribute is depending on the partial primary key then it should determine the other attributes for an instance of the entity.
- The partial dependencies should be removed from the data model.
Third normal form (3NF):
- The value of any non-primary key attributes will not depend on any other non-primary key attributes.
- If any non-primary key attributes depend on any other non-primary key attribute then it should be moved or deleted.
- It is termed as transitive dependency.
Partial dependency:
A partial dependency exists at that time of an attributes depends only a part of primary key. This dependency is related with 1st normal form.
Transitive dependency:
A transitive dependency exists at that time of an attributes depends on another attribute which is not part of primary key.
Functional dependency:
An association between two attributes or two set of attributes in a same relational database table, which is having some constraints is known as functional dependency.
- In a table one attribute is functionally dependent on another attribute to take one value.
c.
Explanation of Solution
Construct the dependency diagram by removing all transitive dependencies:
The new dependency diagram is represented by removing all transitive dependencies in INVOICE table.
First table:
The relational schema for first table is given below:
3NF(INV_NUM, PROD_NUM, QUANT_SOLD)
- Here, “INV_NUM” and “PROD_NUM” indicates the primary keys.
- The relation is in third normal form (3NF), since there is no transitive dependency and no repeated attributes.
The representation of dependency diagram removes all partial dependencies in first table are shown below:
Second table:
The relational schema for second table is given below:
3NF(INV_NUM, SALE_DATE)
- Here, “INV_NUM” indicates the primary key.
- The relation is in third normal form (3NF), since there is no transitive dependency and no repeated attributes.
The representation of dependency diagram removes all transitive dependencies in second table are shown below:
Third table:
The relational schema for third table is given below:
3NF(VEND_CODE, VEND_NAME)
- Here, “VEND_CODE” indicates the primary key.
- The relation is in third normal form (3NF), since there is no transitive dependency and no repeated attributes.
The representation of dependency diagram removes all transitive dependencies in third table are shown below:
Fourth table:
The relational schema for final table is given below:
2NF(PROD_NUM, PROD_LABEL, VEND_CODE, PROD_PRICE)
- Here, “PROD_NUM” indicates the primary key.
- The relation is in third normal form (3NF), since there is no transitive dependency and no repeated attributes.
The representation of dependency diagram removes all transitive dependencies are shown below:
d.
Explanation of Solution
The representation of Crow’s Foot Entity Relational Diagram (ERD) is shown below:
The following data model shows the solution for the given question.
Explanation:
- In the above data model, one invoice can contains many invoice line.
- The “INVOICE” entity contains the “INV_NUM” and “SALE_DATE” attributes.
- The primary key of “INVOICE” entity is “INV_NUM”.
- The “INV_LINE” entity contains the “INV_NUM”, “PROD_NUM” and “QUANT_SOLD” attributes.
- The primary and foreign key of this entity is “INV_NUM”.
- The foreign key of this entity is “PROD_NUM”.
- The “INVOICE” entity contains the “INV_NUM” and “SALE_DATE” attributes.
- The product is written in more than one invoice line.
- The “PRODUCT” entity contains the “PROD_NUM”, “VEND_CODE”, “PROD_LABEL”, and “PROD_PRICE” attributes.
- The primary key of “PROD_NUM” for this entity.
- The foreign key of this entity is “VEND_CODE”.
- The “PRODUCT” entity contains the “PROD_NUM”, “VEND_CODE”, “PROD_LABEL”, and “PROD_PRICE” attributes.
- The vendor supplies more than one product.
- The “VENDOR” entity contains the “VEND_CODE” and “VEND_NAME” attributes.
- The primary key of “VEND_CODE” entity.
- The “VENDOR” entity contains the “VEND_CODE” and “VEND_NAME” attributes.
Want to see more full solutions like this?
Chapter 6 Solutions
Bundle: Database Systems: Design, Implementation, & Management, 13th + Mindtap Mis, 1 Term (6 Months) Printed Access Card
- Using the STUDENT table structure in picture, do the following: 1. Write the relational schema, draw its dependency diagram and identify all dependencies, including all partial and transitive dependencies. You can assume that the table does not contain repeating groups and that any invoice number may reference more than one product. (Hint: This table uses a composite primary key.) 2. Remove all partial dependencies, write the relational schema, and draw the new dependency diagrams. Identify the normal forms for each table structure you created. 3. Remove all transitive dependencies, write the relational schema, and draw the new dependency diagrams. Also identify the normal forms for each table structure you created. 4. Draw the Crow’s Foot ERD.arrow_forwardBased on the following table given , a)Write a 1NF relational schema and identify the partial and transitive dependencies. b)Write the relational schema for 2NF and 3NF. *Not explanation*arrow_forwardUsing your knowledge of the college environment, determine the functional dependencies that exist in the following table. After determining the functional dependencies, convert this table to an equivalent collection of tables that are in third normal form. Do not create a diagram of the tables. Instead use the symbolism like that found in the textbook when showing functional dependencies. (StudentNum, StudentName, NumCredits, AdvisorNum, AdvisorName, DeptNum, DeptName, CourseNum, Description, Term, Grade)arrow_forward
- Convert the diagram into a set of relational tables. The tables must be in 3NF. All referential integrity and functional dependencies must be indicated accurately in EITHER of the following 2 ways: Draw lines for referential integrity and for functional dependencies as belows. 1. Show referential integrity as follows: Supplier(S#, Sname, City, Status); Part(P#, Pname, Color, Weight, City); SP(S#, P#, QTY) Foreign key (S#) References Supplier, Foreign key (P#) References Part; 2. Show functional dependencies as follows: B → C CD → Earrow_forwardFor each table, identify the primary key and the foreign key(s). If a table does not have a foreign key, write None in the space provided. Do the tables exhibit entity integrity and referential integrity? Answer yes or no and then explain your answer. In the case of Referential Integrity write NA (Not Applicable) if the table does not have a foreign key. iii. Describe the type(s) of relationship(s) between STORE and REGION Create the ERD to show the relationship between STORE and REGION.6 Describe the type(s) of relationship(s) between EMPLOYEE and STORE. (Hint: Each store employs many employees, one of whom manages the store.) Draw the ERD to show the relationships among EMPLOYEE, STORE and REGION.arrow_forwardYou have to normalize database tables to 3rd Normal form for the data presented in the next page. The data represents sales transaction details. Dependency diagram of the table after converting to 1NF indicating all the dependencies Dependency diagram for each table after converting to 2NF indicating all the dependencies Dependency diagrams of each table after converting to 3NF indicating all the dependenciesarrow_forward
- Based on the picture, create the ERD for this database. Then explain if the tables exhibit referential or entity integrity? Finally, Identify the TRUCK table’s candidate keysarrow_forwardUse the database shown in Figure P3.1 to answer the questions below:A. For each table, identify the primary key and the foreign key(s). If a table doesnot have a foreign key, write None.B. Do the tables exhibit entity integrity? Answer yes or no, and then explainyour answer.C. Do the tables exhibit referential integrity? Answer yes or no, and then explainyour answer. Write NA (Not Applicable) if the table does not have a foreignkey.D. Describe the type(s) of relationship(s) between STORE and REGION.E. Create the ERD to show the relationship between STORE and REGION.F. Create the relational diagram to show the relationship between STORE andREGION.G. Describe the type(s) of relationship(s) between EMPLOYEE and STORE.(Hint: Each store employs many employees, one of whom manages the store.)H. Create the ERD to show the relationships among EMPLOYEE, STORE, andREGION.I. Create the relational diagram to show the relationships among EMPLOYEE,STORE, and REGION.arrow_forward
- Database Systems: Design, Implementation, & Manag...Computer ScienceISBN:9781305627482Author:Carlos Coronel, Steven MorrisPublisher:Cengage LearningDatabase Systems: Design, Implementation, & Manag...Computer ScienceISBN:9781285196145Author:Steven, Steven Morris, Carlos Coronel, Carlos, Coronel, Carlos; Morris, Carlos Coronel and Steven Morris, Carlos Coronel; Steven Morris, Steven Morris; Carlos CoronelPublisher:Cengage Learning