A. TRUE-FALSE: GROUP 2 PRACTICE EXAMPLES FOR THE REVIEW QUIZ:

Save this PDF as:
 WORD  PNG  TXT  JPG

Size: px
Start display at page:

Download "A. TRUE-FALSE: GROUP 2 PRACTICE EXAMPLES FOR THE REVIEW QUIZ:"

Transcription

1 GROUP 2 PRACTICE EXAMPLES FOR THE REVIEW QUIZ: Review Quiz will contain very similar question as below. Some questions may even be repeated. The order of the questions are random and are not in order of importance or difficulty level. There may be few terminologies unknown to you. Read those from your text (chapter 5). All the concepts are covered in chapter 5 of your text. We will also discuss the new terminologies in the class. (the following questions are covered from your text) A. TRUE-FALSE: 1. A relation is a two-dimensional table. 2. Rows are called attributes. 3. Columns are called tuples. 4. A functional dependency is a relationship between or among attributes. 5. The known or given attribute is called the determinant in a functional dependency. 6. The relationship in a functional dependency is one-to-one (1:1). 7. If a composite attribute is a determinant, then the individual attributes also functional determine the same attribute as the composite attribute. 8. A key is a group of one or more attributes that uniquely identifies a row. 9. The selection of the attributes to use for the key is determined by the database programmers. 10. Rows in a relation must be unique. 11. A deletion anomaly occurs when deleting one entity results in deleting facts about another entity. 12. An insertion anomaly occurs when we cannot insert some data into the database without inserting another entity first. 13. Modification anomalies do not occur in tables that meet the definition of a relation. 14. Normalization is the process of splitting a relation into two or more relations. 15. Relations are classified into normal forms, based on the type of modification anomalies to which they are vulnerable. 16. A table of data that meets the minimum definition of a relation is automatically in first normal form. 17. The order of the rows in a relation is determined by the key chosen. 18. A relation is in first normal form if all of its non-key attributes are dependent on part of the key. 19. A relation is in second normal form if all of its non-key attributes are dependent on all of the key. 20. A transitive dependency occurs when one non-key attribute determines another non-key attribute. 21. A relation can be in third normal form without being in second normal form. 22. A relation often has two or more attributes or attribute collections that can be a key. 23. A relation is in Boyce-Codd normal form if every determinant is a candidate key. 24. A multivalued dependency occurs when an attribute that has multiple values depends on another attribute. 25. Fifth normal form is the highest normal form. 26. A relation can be converted into domain/key normal form using an algorithm specified by R. Fagin. 27. A relation in domain/key normal form is guaranteed to have no modification anomalies. 28. Two attributes in a relation can determine each other. 29. If attribute A determines B, but B does not determine A, the relationship among their data values is one-toone. 30. Normalized relations are sometimes de-normalized to improve performance.

2 B. MULTIPLE-CHOICE 31. A relation is analogous to a: a. file b. field c. record d. row e. column 32. A tuple is analogous to a: a. file b. row c. column d. field e. table 33. An attribute is analogous to a: a. field b. file c. row d. table e. record 34. In a relation: a. the order of the rows and the columns is significant b. the order of the rows is significant, but the order of the columns is not c. the order of the columns is significant, but the order of the rows is not d. neither the order of the rows nor the columns is significant e. the order of the rows and the columns is specified when the relation is defined 35. In a functional dependency, the determinant: a. will be paired with one value of the dependent attribute b. may be paired with one or more values of the dependent attribute c. may consist of more than one attribute d. a and c e. b and c 36. When the determinant contains two attributes: a. the first attribute determines the dependent attribute b. the second attribute determines the dependent attribute c. both attributes determine the dependent attribute d. either the first or second attribute determines the dependent attribute e. the first attribute determines the second 37. A key in a relation: a. may not functionally determine any attribute in the row b. functionally determines only one attribute in the row c. functionally determines at least one attribute in the row d. functionally determines all the attributes in the row e. functionally determines all duplicate rows 38. An anomaly in a relation is: a. an unusual data value b. a duplicate data value caused by changing the data c. an undesirable consequence of changing the data d. an error in the design

3 e. a conflict between the users' and developers' views 39. Restrictions on operations on a relation are called: a. deletion anomalies b. insertion anomalies c. modification anomalies d. domains e. referential integrity constraints 40. The normalization process generally: a. reduces the number of relations b. increases the number of relations c. reduces the number of functional dependencies d. increases the number of functional dependencies e. reduces the number of duplicate rows 41. A relation is automatically in: a. First Normal Form b. Second Normal Form c. Third Normal Form d. Boyce-Codd Normal Form e. Fourth Normal Form 42. A relation is in second normal form if all its non-key attributes are: a. dependent on part of the key b. dependent on all of the key c. independent of the key d. independent of each other e. independent of any other relation 43. A relation is in third normal form if all its non-key attributes are: a. dependent on part of the key b. dependent on all of the key c. independent of the key d. independent of each other e. independent of any other relation 44. A relation is in Boyce-Codd normal form if: a. every determinant is a candidate key b. every determinant is a primary key c. every attribute is a candidate key d. there is more than one candidate key e. there is more than one primary key 45. The primary key is: a. selected by the developers b. selected by the users c. automatically determined by the design d. determined by the DBMS e. determined by the sequence selected for the rows 46. A multivalued dependency exists when a relation has: a. at least two attributes, both of them are multivalued, and their values depend on each other b. at least two attributes, one of them is multivalued, and its value depends on the other c. at least three attributes, two of them are multivalued, and their values depend on only the third attribute d. at least three attributes, one of them is multivalued, and its value depends on the other two attributes

4 e. at least three attributes, all of them are multivalued, and their values depend on each other 47. A relation is in fourth normal form if it is in BCNF and it has no: a. transitive dependencies b. multivalued dependencies c. deletion anomalies d. insertion anomalies e. referential integrity conflicts 48. A relation is in domain/key normal form if: a. every key of the relation is a logical consequence of the definition of constraints and determinants b. every key of the relation is a logical consequence of the definition of constraints and domains c. every constraint on the relation is a logical consequence of the definition of keys and determinants d. every constraint on the relation is a logical consequence of the definition of keys and domains e. every domain of the relation is a logical consequence of the definition of keys and constraints 49. The advantage of having a relation in domain/key normal form is that: a. it takes less storage space than other normal forms b. it is easily obtained from Boyce-Codd normal form c. there is an algorithm for obtaining DK/NF d. it is obtained by enforcing referential integrity constraints e. it is guaranteed to have no modification anomalies 50. Synthesizing relations means that the developers start with a: a. relation and normalize it b. relation and determine its functional dependencies c. set of attributes and determine what relations should be formed d. set of attributes and normalize them e. set of attributes and remove any modification anomalies 51. If two attributes A and B have a one-to-one attribute relationship, it would be shown as: 52. If two attributes A and B have a many-to-one attribute relationship, it would be shown as: 53. If two attributes A and B have a many-to-many attribute relationship, it would be shown as: 54. When a relation has a key consisting of multiple attributes, you can add a new attribute to the relation: a. without any restriction b. so long as it is functionally dependent on part of the key c. so long as it is functionally dependent on all of the key

5 d. so long as it is functionally dependent on a non-key attribute e. so long as it is a candidate key 55. Relations should be normalized to the greatest extent possible except when: a. it would take too long b. performance would be adversely affected c. the database is too large d. the DBMS can't support the restrictions e. data duplication is desired C. FILL-IN BLANKS: 56. A is a two-dimensional table. 57. Rows are called. 58. Columns are called. 59. A is a relationship between or among attributes. 60. The known or given attribute in a functional dependency is called the. 61. A is a group of one or more attributes that uniquely identifies a row. 62. is the process of redefining or splitting a relation into two or more relations that have more desirable properties. 63. For some relations, changing the data can have undesirable consequences, called. 64. A occurs when deleting facts about one entity causes facts about another entity to be deleted. 65. An occurs when we can't insert facts about one entity until we insert facts about another entity. 66. require that before an attribute of a relation can be stored as an attribute in another relation, the value of the attribute must be stored in the first relation. 67. Relations can be classified into classes called, based on the types of modification anomalies to which they are vulnerable. 68. Any table of data that meets the definition of a relation is said to be in. 69. A relation is in if all its non-key attributes are dependent on the entire key. 70. A relation is in third normal form if it is in second normal form and has no. 71. Two or more attributes or attribute collections that can be a key are called. 72. The attribute or attribute collection which is used to uniquely identify each row is called the. 73. A relation is in Boyce-Codd normal form if every is a candidate key. 74. A exists when a relation has at least three attributes, two of them are multivalued, and their values depend on only the third attribute. 75. A relation is in if every constraint on the relation is a logical consequence of the definition of keys and domains. 76. If two attributes have a, they functionally determine each other. 77. If attribute A determines B, but B does not determine A, the relationship among their data values is. 78. If attribute A does not determine B and B does not determine A, the relationship among their data values is. 79. Relations are sometimes purposely left unnormalized or are normalized and then de-normalized in order to. 80. In some cases, creating is preferred to the standard normalization techniques. 81. Describe the relationship between functional dependencies, keys, and uniqueness. 82. Describe the different types of modification anomalies. 83. What is meant by a referential integrity constraint? 84. Give the requirements for a table to be in First, Second, and Third Normal forms. 85. Give the requirements for a table to be in Domain/Key Normal Form, and give the advantage and the disadvantage of the technique.

Chapter 5: Logical Database Design and the Relational Model Part 2: Normalization. Introduction to Normalization. Normal Forms.

Chapter 5: Logical Database Design and the Relational Model Part 2: Normalization. Introduction to Normalization. Normal Forms. Chapter 5: Logical Database Design and the Relational Model Part 2: Normalization Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden Robert C. Nickerson ISYS

More information

MCQs~Databases~Relational Model and Normalization http://en.wikipedia.org/wiki/database_normalization

MCQs~Databases~Relational Model and Normalization http://en.wikipedia.org/wiki/database_normalization http://en.wikipedia.org/wiki/database_normalization Database normalization is the process of organizing the fields and tables of a relational database to minimize redundancy. Normalization usually involves

More information

DATABASE SYSTEMS. Chapter 7 Normalisation

DATABASE SYSTEMS. Chapter 7 Normalisation DATABASE SYSTEMS DESIGN IMPLEMENTATION AND MANAGEMENT INTERNATIONAL EDITION ROB CORONEL CROCKETT Chapter 7 Normalisation 1 (Rob, Coronel & Crockett 978184480731) In this chapter, you will learn: What normalization

More information

Section 4: Logical Data Modelling

Section 4: Logical Data Modelling 2. The Logical Data Model Section 4: Logical Data Modelling As part of Requirements Analysis and Structuring, the data analyst builds a conceptual data model, which includes ER diagrams and process models.

More information

Inf202 Introduction to Data and Databases (Spring 2011)

Inf202 Introduction to Data and Databases (Spring 2011) Inf202 Introduction to Data and Databases (Spring 2011) Jagdish S. Gangolly Informatics CCI SUNY Albany March 1, 2011 Database Design The relational Data Model Relational Data structure (Table) Relational

More information

Data Model ing Essentials

Data Model ing Essentials Data Model ing Essentials Third Edition Graeme C. Simsion and Graham C. Witt MORGAN KAUFMANN PUBLISHERS AN IMPRINT OF ELSEVIER AMSTERDAM BOSTON LONDON NEW YORK OXFORD PARIS SAN DIEGO SAN FRANCISCO SINGAPORE

More information

DATABASE MANAGEMENT SYSTEMS. Question Bank:

DATABASE MANAGEMENT SYSTEMS. Question Bank: DATABASE MANAGEMENT SYSTEMS Question Bank: UNIT 1 1. Define Database? 2. What is a DBMS? 3. What is the need for database systems? 4. Define tupule? 5. What are the responsibilities of DBA? 6. Define schema?

More information

Concepts of Database Management Seventh Edition. Chapter 6 Database Design 2: Design Method

Concepts of Database Management Seventh Edition. Chapter 6 Database Design 2: Design Method Concepts of Database Management Seventh Edition Chapter 6 Database Design 2: Design Method Objectives Discuss the general process and goals of database design Define user views and explain their function

More information

Introduction to normalization. Introduction to normalization

Introduction to normalization. Introduction to normalization Introduction to normalization Lecture 4 Instructor Anna Sidorova Agenda Presentation Review of relational models, in class exersise Introduction to normalization In-class exercises Discussion of HW2 1

More information

Relational Database Design

Relational Database Design Relational Database Design Jan Chomicki University at Buffalo Jan Chomicki () Relational database design 1 / 16 Outline 1 Functional dependencies 2 Normal forms 3 Multivalued dependencies Jan Chomicki

More information

Chapter 15 Basics of Functional Dependencies and Normalization for Relational Databases

Chapter 15 Basics of Functional Dependencies and Normalization for Relational Databases Chapter 15 Basics of Functional Dependencies and Normalization for Relational Databases Copyright 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 15 Outline Informal Design Guidelines

More information

CS 377 Database Systems. Database Design Theory and Normalization. Li Xiong Department of Mathematics and Computer Science Emory University

CS 377 Database Systems. Database Design Theory and Normalization. Li Xiong Department of Mathematics and Computer Science Emory University CS 377 Database Systems Database Design Theory and Normalization Li Xiong Department of Mathematics and Computer Science Emory University 1 Relational database design So far Conceptual database design

More information

Introduction to Computing. Lectured by: Dr. Pham Tran Vu t.v.pham@cse.hcmut.edu.vn

Introduction to Computing. Lectured by: Dr. Pham Tran Vu t.v.pham@cse.hcmut.edu.vn Introduction to Computing Lectured by: Dr. Pham Tran Vu t.v.pham@cse.hcmut.edu.vn Databases The Hierarchy of Data Keys and Attributes The Traditional Approach To Data Management Database A collection of

More information

Microsoft MTA Database Administration Fundamentals

Microsoft MTA Database Administration Fundamentals 1 Microsoft - 98-364 MTA Database Administration Fundamentals QUESTION: 1 John works as a Database Administrator for Bluewell Inc. The company has a SQL Server database. A table in the database has a candidate

More information

DBMS Interview Questions

DBMS Interview Questions DBMS Interview Questions 1. What is database? A database is a collection of information that is organized. So that it can easily be accessed, managed, and updated. 2. What is DBMS? DBMS stands for Database

More information

DATABASE NORMALIZATION

DATABASE NORMALIZATION DATABASE NORMALIZATION Normalization: process of efficiently organizing data in the DB. RELATIONS (attributes grouped together) Accurate representation of data, relationships and constraints. Goal: - Eliminate

More information

Systems Analysis and Design

Systems Analysis and Design Systems Analysis and Design Slides adapted from Jeffrey A. Hoffer, University of Dayton Joey F. George, Florida State University Joseph S. Valacich, Washington State University Modern Systems Analysis

More information

Title: ENHANCEMENT OF ERD. Research by: Student Name : Wafa Ali Edrees. Student Id : 201130061. Collage Of Computer Science and Information System

Title: ENHANCEMENT OF ERD. Research by: Student Name : Wafa Ali Edrees. Student Id : 201130061. Collage Of Computer Science and Information System Title: ENHANCEMENT OF ERD Research by: Student Name : Wafa Ali Edrees Student Id : 201130061 Collage Of Computer Science and Information System Level : 5 Teacher : Arshia Arjumand Banu 1 ENHANCEMENT OF

More information

The Relational Database Model

The Relational Database Model The Relational Database Model 1 Describing how to tune a relational database model would not be complete without a description of normalization. I have attempted to simplify normalization. When I attended

More information

Normalization. Functional Dependence. Normalization. Normalization. GIS Applications. Spring 2011

Normalization. Functional Dependence. Normalization. Normalization. GIS Applications. Spring 2011 Normalization Normalization Normalization is a foundation for relational database design Systematic approach to efficiently organize data in a database GIS Applications Spring 2011 Objectives Minimize

More information

Part 6. Normalization

Part 6. Normalization Part 6 Normalization Normal Form Overview Universe of All Data Relations (normalized / unnormalized 1st Normal Form 2nd Normal Form 3rd Normal Form Boyce-Codd Normal Form (BCNF) 4th Normal Form 5th Normal

More information

Chapter 6. Database Tables & Normalization. The Need for Normalization. Database Tables & Normalization

Chapter 6. Database Tables & Normalization. The Need for Normalization. Database Tables & Normalization Chapter 6 Database Tables & Normalization Objectives: to learn What normalization is and what role it plays in the database design process About the normal forms 1NF, 2NF, 3NF, BCNF, and 4NF How normal

More information

Physical Database Design Process. Physical Database Design Process. Major Inputs to Physical Database. Components of Physical Database Design

Physical Database Design Process. Physical Database Design Process. Major Inputs to Physical Database. Components of Physical Database Design Physical Database Design Process Physical Database Design Process The last stage of the database design process. A process of mapping the logical database structure developed in previous stages into internal

More information

Normalization of Database

Normalization of Database Normalization of Database UNIT-4 Database Normalisation is a technique of organizing the data in the database. Normalization is a systematic approach of decomposing tables to eliminate data redundancy

More information

BCA. Database Management System

BCA. Database Management System BCA IV Sem Database Management System Multiple choice questions 1. A Database Management System (DBMS) is A. Collection of interrelated data B. Collection of programs to access data C. Collection of data

More information

SQL Server. 1. What is RDBMS?

SQL Server. 1. What is RDBMS? SQL Server 1. What is RDBMS? Relational Data Base Management Systems (RDBMS) are database management systems that maintain data records and indices in tables. Relationships may be created and maintained

More information

Database design 1 The Database Design Process: Before you build the tables and other objects that will make up your system, it is important to take time to design it. A good design is the keystone to creating

More information

Database Management System

Database Management System Database Management System Normalization (Unit - IV) NORMALIZATION While designing a database out of an entity relationship model, the main problem existing in that raw database is redundancy. Redundancy

More information

Q4. What are data model? Explain the different data model with examples. Q8. Differentiate physical and logical data independence data models.

Q4. What are data model? Explain the different data model with examples. Q8. Differentiate physical and logical data independence data models. FAQs Introduction to Database Systems and Design Module 1: Introduction Data, Database, DBMS, DBA Q2. What is a catalogue? Explain the use of it in DBMS. Q3. Differentiate File System approach and Database

More information

Database Management System Dr. S. Srinath Department of Computer Science & Engineering Indian Institute of Technology, Madras Lecture No.

Database Management System Dr. S. Srinath Department of Computer Science & Engineering Indian Institute of Technology, Madras Lecture No. Database Management System Dr. S. Srinath Department of Computer Science & Engineering Indian Institute of Technology, Madras Lecture No. # 8 Functional Dependencies and Normal Forms Two different kinds

More information

a. Write a query to generate the number of charter flights to the same destination and shows the results in alphabetic order.

a. Write a query to generate the number of charter flights to the same destination and shows the results in alphabetic order. CS 631 _ DBMS Sample Final Exam Questions Question #1: Using the data given in the AviaCo database, perform the following queries and show the expected results: a. Write a query to generate the number

More information

Copyright 2007 Ramez Elmasri and Shamkant B. Navathe. Slide 10-1

Copyright 2007 Ramez Elmasri and Shamkant B. Navathe. Slide 10-1 Slide 10-1 Chapter 10 Functional Dependencies and Normalization for Relational Databases Chapter Outline 1 Informal Design Guidelines for Relational Databases 1.1Semantics of the Relation Attributes 1.2

More information

Functional Dependency and Normalization for Relational Databases

Functional Dependency and Normalization for Relational Databases Functional Dependency and Normalization for Relational Databases Introduction: Relational database design ultimately produces a set of relations. The implicit goals of the design activity are: information

More information

1/24/2010 DATABASE DESIGN AND DEVELOPMENT: A VISUAL APPROACH. Normalized vs. Denormalized. Denormalized Sample Data. Chapter 4 Normalization

1/24/2010 DATABASE DESIGN AND DEVELOPMENT: A VISUAL APPROACH. Normalized vs. Denormalized. Denormalized Sample Data. Chapter 4 Normalization DATABASE DESIGN AND DEVELOPMENT: A VISUAL APPROACH Raymond Frost John Day Craig Van Slyke Normalization 1 Normalized vs. Denormalized Exhibit 4-1: Arcade Database Normalized vs. Denormalized Design 2 Denormalized

More information

Database Design. Marta Jakubowska-Sobczak IT/ADC based on slides prepared by Paula Figueiredo, IT/DB

Database Design. Marta Jakubowska-Sobczak IT/ADC based on slides prepared by Paula Figueiredo, IT/DB Marta Jakubowska-Sobczak IT/ADC based on slides prepared by Paula Figueiredo, IT/DB Outline Database concepts Conceptual Design Logical Design Communicating with the RDBMS 2 Some concepts Database: an

More information

Concepts of Database Management, Fifth Edition. Chapter 6: Database Design 2: Design Methodology

Concepts of Database Management, Fifth Edition. Chapter 6: Database Design 2: Design Methodology Concepts of Database Management, Fifth Edition Chapter 6: Database Design 2: Design Methodology Objectives Discuss the general process and goals of database design Define user views and explain their function

More information

Fundamentals of Database System

Fundamentals of Database System Fundamentals of Database System Chapter 4 Normalization Fundamentals of Database Systems (Chapter 4) Page 1 Introduction To Normalization In general, the goal of a relational database design is to generate

More information

COSC344 Database Theory and Applications. Lecture 9 Normalisation. COSC344 Lecture 9 1

COSC344 Database Theory and Applications. Lecture 9 Normalisation. COSC344 Lecture 9 1 COSC344 Database Theory and Applications Lecture 9 Normalisation COSC344 Lecture 9 1 Overview Last Lecture Functional Dependencies This Lecture Normalisation Introduction 1NF 2NF 3NF BCNF Source: Section

More information

Database Design and Normalization

Database Design and Normalization Database Design and Normalization CPS352: Database Systems Simon Miner Gordon College Last Revised: 9/27/12 Agenda Check-in Functional Dependencies (continued) Design Project E-R Diagram Presentations

More information

Database Normalization Database normalization is the process of removing redundant data from your tables in to improve storage efficiency, data integr

Database Normalization Database normalization is the process of removing redundant data from your tables in to improve storage efficiency, data integr Normalization Database Normalization Database normalization is the process of removing redundant data from your tables in to improve storage efficiency, data integrity, and scalability. In the relational

More information

Announcements. SQL is hot! Facebook. Goal. Database Design Process. IT420: Database Management and Organization. Normalization (Chapter 3)

Announcements. SQL is hot! Facebook. Goal. Database Design Process. IT420: Database Management and Organization. Normalization (Chapter 3) Announcements IT0: Database Management and Organization Normalization (Chapter 3) Department coin design contest deadline - February -week exam Monday, February 1 Lab SQL SQL Server: ALTER TABLE tname

More information

Functional Dependencies and Finding a Minimal Cover

Functional Dependencies and Finding a Minimal Cover Functional Dependencies and Finding a Minimal Cover Robert Soulé 1 Normalization An anomaly occurs in a database when you can update, insert, or delete data, and get undesired side-effects. These side

More information

Normalization. Normalization. Normalization. Data Redundancy

Normalization. Normalization. Normalization. Data Redundancy Normalization Normalization o Main objective in developing a logical data model for relational database systems is to create an accurate representation of the data, its relationships, and constraints.

More information

Chapter 10 Functional Dependencies and Normalization for Relational Databases

Chapter 10 Functional Dependencies and Normalization for Relational Databases Chapter 10 Functional Dependencies and Normalization for Relational Databases Copyright 2004 Pearson Education, Inc. Chapter Outline 1 Informal Design Guidelines for Relational Databases 1.1Semantics of

More information

Normalization in OODB Design

Normalization in OODB Design Normalization in OODB Design Byung S. Lee Graduate Programs in Software University of St. Thomas St. Paul, Minnesota bslee@stthomas.edu Abstract When we design an object-oriented database schema, we need

More information

Optimum Database Design: Using Normal Forms and Ensuring Data Integrity. by Patrick Crever, Relational Database Programmer, Synergex

Optimum Database Design: Using Normal Forms and Ensuring Data Integrity. by Patrick Crever, Relational Database Programmer, Synergex Optimum Database Design: Using Normal Forms and Ensuring Data Integrity by Patrick Crever, Relational Database Programmer, Synergex Printed: April 2007 The information contained in this document is subject

More information

Theory of Relational Database Design and Normalization

Theory of Relational Database Design and Normalization Theory of Relational Database Design and Normalization (Based on Chapter 14 and some part of Chapter 15 in Fundamentals of Database Systems by Elmasri and Navathe, Ed. 3) 1 Informal Design Guidelines for

More information

Database Systems - Introduction to Databases and Data Warehouses. Copyright (c) 2014 Pearson Education, Inc.

Database Systems - Introduction to Databases and Data Warehouses. Copyright (c) 2014 Pearson Education, Inc. Database Systems - Introduction to Databases and Data Warehouses Copyright (c) 2014 Pearson Education, Inc. INTRODUCTION Relational database model - logical database model that represents a database as

More information

Chapter 14. Normalization

Chapter 14. Normalization Chapter 14 Normalization Materials To Have Handy A paper copy of the StaffBranch relation (pg. 369 of the textbook and on or about slide 9) A paper copy of the Staff Branch function dependencies (pg. 375

More information

SUMMARY OF MODULE A conceptual model of data used in an application is obtained by using an entity

SUMMARY OF MODULE A conceptual model of data used in an application is obtained by using an entity SUMMARY OF MODULE 8 1. A conceptual model of data used in an application is obtained by using an entity relationship model (E-R model). 2. Entities specify distinct real world items in an application,

More information

Chapter 5: FUNCTIONAL DEPENDENCIES AND NORMALIZATION FOR RELATIONAL DATABASES

Chapter 5: FUNCTIONAL DEPENDENCIES AND NORMALIZATION FOR RELATIONAL DATABASES 1 Chapter 5: FUNCTIONAL DEPENDENCIES AND NORMALIZATION FOR RELATIONAL DATABASES INFORMAL DESIGN GUIDELINES FOR RELATION SCHEMAS We discuss four informal measures of quality for relation schema design in

More information

Chapter 10. Functional Dependencies and Normalization for Relational Databases

Chapter 10. Functional Dependencies and Normalization for Relational Databases Chapter 10 Functional Dependencies and Normalization for Relational Databases Chapter Outline 1 Informal Design Guidelines for Relational Databases 1.1Semantics of the Relation Attributes 1.2 Redundant

More information

LOGICAL DATABASE DESIGN

LOGICAL DATABASE DESIGN MODULE 8 LOGICAL DATABASE DESIGN OBJECTIVE QUESTIONS There are 4 alternative answers to each question. One of them is correct. Pick the correct answer. Do not guess. A key is given at the end of the module

More information

1.264 Lecture 10. Data normalization

1.264 Lecture 10. Data normalization 1.264 Lecture 10 Data normalization Next class: Read Murach chapters 1-3. Exercises due after class Make sure you ve downloaded and run the.sql file to create the database we ll be using in the next two

More information

IT2305 Database Systems I (Compulsory)

IT2305 Database Systems I (Compulsory) Database Systems I (Compulsory) INTRODUCTION This is one of the 4 modules designed for Semester 2 of Bachelor of Information Technology Degree program. CREDITS: 04 LEARNING OUTCOMES On completion of this

More information

National Unit Specification: general information. Relational Database Systems (Higher) NUMBER DM4K 12. Information Systems (Higher)

National Unit Specification: general information. Relational Database Systems (Higher) NUMBER DM4K 12. Information Systems (Higher) National Unit Specification: general information NUMBER DM4K 12 COURSE Information Systems (Higher) SUMMARY This Unit is designed to develop knowledge and understanding of the principles of relational

More information

Logical Database Design (Part 2) CS 122: Database Systems Second Semester,

Logical Database Design (Part 2) CS 122: Database Systems Second Semester, Logical Database Design (Part 2) CS 122: Database Systems Second Semester, 2012-2013 Transforming Associative Entities If an identifier is not assigned, the default primary key for the association relation

More information

Lecture 2 Normalization

Lecture 2 Normalization MIT 533 ระบบฐานข อม ล 2 Lecture 2 Normalization Walailuk University Lecture 2: Normalization 1 Objectives The purpose of normalization The identification of various types of update anomalies The concept

More information

Topic 5.1: Database Tables and Normalization

Topic 5.1: Database Tables and Normalization Topic 5.1: Database Tables and Normalization What is Normalization? Normalization is a process for evaluating and correcting table structures to minimize data redundancies, thereby helping to eliminate

More information

Aveek Gupta, CISA. IPCC Paper 7A: Information Technology Chapter 2

Aveek Gupta, CISA. IPCC Paper 7A: Information Technology Chapter 2 Aveek Gupta, CISA IPCC Paper 7A: Information Technology Chapter 2 * DBMS/RDBMS 1 Administration 2 3 4 5 6 6 7 Models DML and DDL Data Dictionaries Distributed DataBases Object Oriented DataBases Client

More information

Database Design for the Uninitiated CDS Brownbag Series CDS

Database Design for the Uninitiated CDS Brownbag Series CDS Database Design for the Uninitiated Paul Litwin FHCRC Collaborative Data Services 1 CDS Brownbag Series This is the ninth in a series of seminars Materials for the series can be downloaded from www.deeptraining.com/fhcrc

More information

Chapter 6: Physical Database Design and Performance. Database Development Process. Physical Design Process. Physical Database Design

Chapter 6: Physical Database Design and Performance. Database Development Process. Physical Design Process. Physical Database Design Chapter 6: Physical Database Design and Performance Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden Robert C. Nickerson ISYS 464 Spring 2003 Topic 23 Database

More information

DBMS. Normalization. Module Title?

DBMS. Normalization. Module Title? Normalization Database Normalization Database normalization is the process of removing redundant data from your tables in to improve storage efficiency, data integrity (accuracy and consistency), and scalability

More information

DBMS QUESTION BANK FOR FYBCA (SEM II) SHORT QUESTIONS: UNIT 1

DBMS QUESTION BANK FOR FYBCA (SEM II) SHORT QUESTIONS: UNIT 1 DBMS QUESTION BANK FOR FYBCA (SEM II) SHORT QUESTIONS: UNIT 1 1. Define domain. 2. What do you mean by total participation in a relationship? 3. Explain strong and weak entity set with example. 4. What

More information

Fundamentals of Database Design

Fundamentals of Database Design Fundamentals of Database Design Zornitsa Zaharieva CERN Data Management Section - Controls Group Accelerators and Beams Department /AB-CO-DM/ 23-FEB-2005 Contents : Introduction to Databases : Main Database

More information

Database Management System Dr. S. Srinath Department of Computer Science & Engineering Indian Institute of Technology, Madras Lecture No.

Database Management System Dr. S. Srinath Department of Computer Science & Engineering Indian Institute of Technology, Madras Lecture No. Database Management System Dr. S. Srinath Department of Computer Science & Engineering Indian Institute of Technology, Madras Lecture No. # 7 ER Model to Relational Mapping Hello and welcome to the next

More information

CS2Bh: Current Technologies. Introduction to XML and Relational Databases. The Relational Model. The relational model

CS2Bh: Current Technologies. Introduction to XML and Relational Databases. The Relational Model. The relational model CS2Bh: Current Technologies Introduction to XML and Relational Databases Spring 2005 The Relational Model CS2 Spring 2005 (LN6) 1 The relational model Proposed by Codd in 1970. It is the dominant data

More information

Database Design Theory: Introduction to Normalization Using Functional and Multivalued Dependencies

Database Design Theory: Introduction to Normalization Using Functional and Multivalued Dependencies Database Design Theory: Introduction to Normalization Using Functional and Multivalued Dependencies Copyright 2012 Ramez Elmasri and Shamkant B. Navathe Chapter Outline 1 Informal Design Guidelines for

More information

1 the relational data model The relational model of data was introduced by E.F. Codd (1970). 1.1 relational model concepts The relational model repres

1 the relational data model The relational model of data was introduced by E.F. Codd (1970). 1.1 relational model concepts The relational model repres database systems formal definitions of the relational data model [03] s. yurttaοs 1 1 the relational data model The relational model of data was introduced by E.F. Codd (1970). 1.1 relational model concepts

More information

CSE 412/598 DATABASE MANAGEMENT COURSE NOTES 3. ENTITY-RELATIONSHIP CONCEPTUAL MODELING

CSE 412/598 DATABASE MANAGEMENT COURSE NOTES 3. ENTITY-RELATIONSHIP CONCEPTUAL MODELING DATABASE MANAGEMENT COURSE NOTES 3. ENTITY-RELATIONSHIP CONCEPTUAL MODELING Department of Computer Science & Engineering Arizona State University 2 Quality of Conceptual Schema Correctness. No syntactic

More information

Database design basics

Database design basics Microsoft Office Access Database design basics Applies to: Microsoft Office Access 2007 A properly designed database provides you with access to up-to-date, accurate information. Because a correct design

More information

Database Systems Data Models & The Relational Model

Database Systems Data Models & The Relational Model Database Systems Data Models & The Relational Model Developing the Database To develop a database you must: Analyze the requirements Logically design the structures Model the data What is a model? Data

More information

Databases What the Specification Says

Databases What the Specification Says Databases What the Specification Says Describe flat files and relational databases, explaining the differences between them; Design a simple relational database to the third normal form (3NF), using entityrelationship

More information

Ken Goldberg Database Lab Notes. There are three types of relationships: One-to-One (1:1) One-to-Many (1:N) Many-to-Many (M:N).

Ken Goldberg Database Lab Notes. There are three types of relationships: One-to-One (1:1) One-to-Many (1:N) Many-to-Many (M:N). Lab 3 Relationships in ER Diagram and Relationships in MS Access MS Access Lab 3 Summary Introduction to Relationships Why Define Relationships? Relationships in ER Diagram vs. Relationships in MS Access

More information

RELATIONAL DATABASE DESIGN. Basic Concepts

RELATIONAL DATABASE DESIGN. Basic Concepts Basic Concepts a database is an collection of logically related records a relational database stores its data in 2-dimensional tables a table is a two-dimensional structure made up of rows (tuples, records)

More information

Database Design and the Reality of Normalisation

Database Design and the Reality of Normalisation Proceedings of the NACCQ 2000 Wellington NZ www.naccq.ac.nz Database Design and the Reality of Normalisation Dave Kennedy ABSTRACT Institute of Technology Christchurch Polytechnic Te Whare Runanga O Otautahi

More information

Normalisation to 3NF. Database Systems Lecture 11 Natasha Alechina

Normalisation to 3NF. Database Systems Lecture 11 Natasha Alechina Normalisation to 3NF Database Systems Lecture 11 Natasha Alechina In This Lecture Normalisation to 3NF Data redundancy Functional dependencies Normal forms First, Second, and Third Normal Forms For more

More information

Normalisation 6 TABLE OF CONTENTS LEARNING OUTCOMES

Normalisation 6 TABLE OF CONTENTS LEARNING OUTCOMES Topic Normalisation 6 LEARNING OUTCOMES When you have completed this Topic you should be able to: 1. Discuss importance of the normalisation in the database design. 2. Discuss the problems related to data

More information

Functional Dependency. Functional Dependence. Database Design

Functional Dependency. Functional Dependence. Database Design Karlstad University Department of Information Systems Adapted for a textbook by Date C. J. An Introduction to Database Systems Pearson Addison Wesley, 2004 Database Design Remigijus GUSTAS Phone: +46-54

More information

IT2304: Database Systems 1 (DBS 1)

IT2304: Database Systems 1 (DBS 1) : Database Systems 1 (DBS 1) (Compulsory) 1. OUTLINE OF SYLLABUS Topic Minimum number of hours Introduction to DBMS 07 Relational Data Model 03 Data manipulation using Relational Algebra 06 Data manipulation

More information

Normalization in Database Design

Normalization in Database Design in Database Design Marek Rychly mrychly@strathmore.edu Strathmore University, @ilabafrica & Brno University of Technology, Faculty of Information Technology Advanced Databases and Enterprise Systems 14

More information

Relational Model CENG 351 1

Relational Model CENG 351 1 Relational Model CENG 351 1 Relational Database: Definitions Relational database: a set of relations Relation: made up of 2 parts: Instance : a table, with rows and columns. #Rows = cardinality, #fields

More information

The Entity Relationship Model and Database Design

The Entity Relationship Model and Database Design The Entity Relationship Model and Database Design CPS352: Database Systems Simon Miner Gordon College Last Revised: 9/20/12 Agenda Check-in The Entity Relationship Model Group Exercise Database Design

More information

Normalization. CIS 3730 Designing and Managing Data. J.G. Zheng Fall 2010

Normalization. CIS 3730 Designing and Managing Data. J.G. Zheng Fall 2010 Normalization CIS 3730 Designing and Managing Data J.G. Zheng Fall 2010 1 Overview What is normalization? What are the normal forms? How to normalize relations? 2 Two Basic Ways To Design Tables Bottom-up:

More information

Database Management System

Database Management System UNIT -6 Database Design Informal Design Guidelines for Relation Schemas; Functional Dependencies; Normal Forms Based on Primary Keys; General Definitions of Second and Third Normal Forms; Boyce-Codd Normal

More information

Chapter 7. ER and EER-to-Relational Mapping

Chapter 7. ER and EER-to-Relational Mapping Chapter 7 ER and EER-to-Relational apping Relational Data odel From a completed E-R diagram, you can translate that schema into a formal data model required by the DBS. Data odel a formal way of describing

More information

Database Normalization. Mohua Sarkar, Ph.D Software Engineer California Pacific Medical Center 415-600-7003 sarkarm@sutterhealth.

Database Normalization. Mohua Sarkar, Ph.D Software Engineer California Pacific Medical Center 415-600-7003 sarkarm@sutterhealth. Database Normalization Mohua Sarkar, Ph.D Software Engineer California Pacific Medical Center 415-600-7003 sarkarm@sutterhealth.org Definition A database is an organized collection of data whose content

More information

Chapter 7: Relational Database Design

Chapter 7: Relational Database Design Chapter 7: Relational Database Design Pitfalls in Relational Database Design Decomposition Normalization Using Functional Dependencies Normalization Using Multivalued Dependencies Normalization Using Join

More information

If it's in the 2nd NF and there are no non-key fields that depend on attributes in the table other than the Primary Key.

If it's in the 2nd NF and there are no non-key fields that depend on attributes in the table other than the Primary Key. Normalization First Normal Form (1st NF) The table cells must be of single value. Eliminate repeating groups in individual tables. Create a separate table for each set of related data. Identify each set

More information

Theory of Relational Database Design and Normalization

Theory of Relational Database Design and Normalization Theory of Relational Database Design and Normalization (Based on Chapter 14 and some part of Chapter 15 in Fundamentals of Database Systems by Elmasri and Navathe) 1 Informal Design Guidelines for Relational

More information

Chapter 5: Logical Database Design and the Relational Model Part 1: Transforming EER Diagrams into Relations Modern Database Management 6 th Edition

Chapter 5: Logical Database Design and the Relational Model Part 1: Transforming EER Diagrams into Relations Modern Database Management 6 th Edition Chapter 5: Logical Database Design and the Relational Model Part 1: into Relations Modern Database Management 6 th Edition Jeffrey A. Hoffer, Mary B. Prescott, Fred R. McFadden Robert C. Nickerson ISYS

More information

Topic: Relationships in ER Diagram and Relationships in MS Access

Topic: Relationships in ER Diagram and Relationships in MS Access MS Access Lab 3 Topic: Relationships in ER Diagram and Relationships in MS Access Summary Introduction to Relationships Why Define Relationships? Relationships in ER Diagram vs. Relationships in MS Access

More information

Bridge from Entity Relationship modeling to creating SQL databases, tables, & relations

Bridge from Entity Relationship modeling to creating SQL databases, tables, & relations 1 Topics for this week: 1. Good Design 2. Functional Dependencies 3. Normalization Readings for this week: 1. E&N, Ch. 10.1-10.6; 12.2 2. Quickstart, Ch. 3 3. Complete the tutorial at http://sqlcourse2.com/

More information

Database Design Methodologies

Database Design Methodologies Critical Success Factors in Database Design Database Design Methodologies o Work interactively with the users as much as possible. o Follow a structured methodology throughout the data modeling process.

More information

Section of DBMS Selection & Evaluation Questionnaire

Section of DBMS Selection & Evaluation Questionnaire Section of DBMS Selection & Evaluation Questionnaire Whitemarsh Information Systems Corporation 2008 Althea Lane Bowie, Maryland 20716 Tele: 301-249-1142 Email: mmgorman@wiscorp.com Web: www.wiscorp.com

More information

Evidence for this unit can only be achieved through actual work in a work environment. Simulation is not permissible for any competence based unit.

Evidence for this unit can only be achieved through actual work in a work environment. Simulation is not permissible for any competence based unit. Unit Title: OCR unit number Data Modelling 18 (L/601/3203) Level: 3 Credit value: 9 Guided learning hours: 75 Unit expiry date: 31/03/2015 Evidence for this unit can only be achieved through actual work

More information

From ER (or EER ) to Relational Schema. Inputs :ER Outputs: Data Model

From ER (or EER ) to Relational Schema. Inputs :ER Outputs: Data Model Mapping Rules From ER (or EER ) to Relational Schema Inputs :ER Outputs: Data Model Prentice Hall, 2002 1 Transforming EER Diagrams into Relations Mapping Regular Entities to Relations 1. Simple attributes:

More information

TIM 50 - Business Information Systems

TIM 50 - Business Information Systems TIM 50 - Business Information Systems Lecture 15 UC Santa Cruz March 1, 2015 The Database Approach to Data Management Database: Collection of related files containing records on people, places, or things.

More information

Introduction to DBMS

Introduction to DBMS CHAPTER 1 Introduction to DBMS In this chapter, you will learn 1.0 Introduction 1.1 History of Database Management System 1.2 Database Architecture 1.3 Database Management System Users 1.4 Role of DBMS

More information

Database Design Basics

Database Design Basics Database Design Basics Table of Contents SOME DATABASE TERMS TO KNOW... 1 WHAT IS GOOD DATABASE DESIGN?... 2 THE DESIGN PROCESS... 2 DETERMINING THE PURPOSE OF YOUR DATABASE... 3 FINDING AND ORGANIZING

More information