Learning outcomes. On successful completion of this unit you will: 1. Understand data models and database technologies.
|
|
- Adrian Mitchell
- 5 years ago
- Views:
Transcription
1
2 Phil Smith
3 Learning outcomes On successful completion of this unit you will: 1. Understand data models and database technologies. (Assignment 1)
4 Recap and setting the scene Before we get to Normalisation we need to learn some more definitions re-visit the roots of relational database theory.
5 Approaches We have already looked at the top down approach to database design achieved using an Entity Relational Model (ERM) along with an Entity relational Diagram (ERD). We have also looked at how we derive a primary key for every entity. (Recap candidate keys, composite keys) We also looked at relationships between entities.
6 Relationship types There are three main kinds of relationships, and it is important to determine both directions of the relationship when modelling the relationships between entities: 1-to-1: Both sides of the relationship have a degree of one and only one. (1-to-1 relationships are rare.) So there is a an enterprise rule here which states 1-to-M: One of the sides has a degree of one or many and the other side has a degree of one and only one. M-to-N: Both sides of the relationship are one or many relationships. Yes it really is M-to-N
7 Relationship types/degree An important property of any relationship is its degree. This is the enterprise rule which applies to the relationship. Suppose we have a relationship between a lecturer and a course (We can name this relationship Teaches ), a lecturer is identified by a lecturername and course identified by courseno. We already know there are three possible kinds of relationship (degree,) each corresponding to different pairs of enterprise rules for the relationship.
8 Relationship types 1:1 relationship Enterprise rules: A lecturer teaches, at most, one course. A course is taught by, at most, one lecturer. This pair of enterprise rules defines Teaches (the relationship) as being a 1:1 relationship. However, this may also include 0:1 and 1:0 A lecturer may not teach any course. A course may not have a lecturer!
9 Relationship types 1:M relationship Enterprise rules: A lecturer may teach many course. A course is taught by, at most, one lecturer. This pair of enterprise rules defines Teaches (the relationship) as being a 1:M (one to many) relationship.
10 Relationship types M:N relationship Enterprise rules: A lecturer may teach many courses. A course may be taught by many lecturer. This pair of enterprise rules defines Teaches (the relationship) as being a M:N (many to many) relationship. We already know that this will need to be corrected.
11 Relationship types There are three main kinds of relationships. Can you describe a fourth? Self-Referencing Relationships: A Special Case. Self-referencing relationships are a special case of a normal table relationship. The only difference is that in this case, there is only one table involved and it is on both sides of the relationship
12 Diagrams used in data analysis Diagrams (ERDs), we have already done this one. determinancy diagrams, A determinancy diagram, sometimes known as a dependency diagram, is a diagram which documents the determinancy or dependency between a set of data items. Determinancy diagrams are particularly used as an aid to database normalization.
13 Diagrams used in data analysis We are building up a set of tools to help us with Normalisation. Lets have a look at a dependency diagram.
14 Diagrams used in data analysis Example dependency diagram.
15 Dependency diagram Task 1 Using the basicdata.xls spreadsheet on the wiki and with reference to the customer spreadsheet. Draw a dependency diagram for the attributes in the sheet. Use what ever software you like. This exercise is part of normalisation but is should allow you to start to understand attribute relationships. This may be use in assignment 1.
16 Diagrams used in data analysis We shall be looking more at dependency diagrams later. There is more to them that the exercise we have completed. Another type of diagram is the data flow diagram.
17 Data flow diagram. A data flow diagram (DFD) is a graphical representation of the "flow" of data through an system, modelling its process aspects. A DFD is often used as a preliminary step to create an overview of the system, which can later be elaborated. A DFD shows what kind of information will be input to and output from the system, where the data will come from and go to, and where the data will be stored. It is a fairly high level diagram which exposes aspects of data which then needs to be further analysed.
18 Data flow diagram. Task 2 Research data flow diagrams and then produce a data flow diagram for an online e-commerce site as created by you in unit 14.
19 Database Normalization Database normalization is the process of removing redundant data from your tables to improve storage efficiency, data integrity, and scalability. In the relational model, methods exist for quantifying how efficient a database is. These classifications are called normal forms (or NF), and there are algorithms for converting a given database between them. Normalization generally involves splitting existing tables into multiple ones, which must be re-joined or linked each time a query is issued.
20 History Edgar F. Codd first proposed the process of normalization and what came to be known as the 1st normal form in his paper A Relational Model of Data for Large Shared Data Banks Codd stated: There is, in fact, a very simple elimination procedure which we shall call normalization. Through decomposition nonsimple domains are replaced by domains whose elements are atomic (nondecomposable) values.
21 Normal Form Edgar F. Codd originally established three normal forms: 1NF, 2NF and 3NF. There are now others that are generally accepted, but 3NF is widely considered to be sufficient for most applications. Most tables when reaching 3NF are also in BCNF (Boyce-Codd Normal Form). Codd had 13 rules, numbered 0 to 12.
22 Normalisation is the process which allows you to winnow out redundant data within your database. This involves restructuring the tables to successively meeting higher forms of Normalization. A properly normalized database should have the following characteristics Scalar values in each fields Absence of redundancy. Definition Minimal use of null values. Minimal loss of information.
23 Definition Normalisation is a bottom up process.
24 Database Tables and Normalization Normalization Process for evaluating and correcting table structures to minimize data redundancies Reduces data anomalies Works through a series of stages called normal forms: First normal form (1NF) Second normal form (2NF) Third normal form (3NF) 24
25 Database Tables and Normalization (continued) Normalization (continued) 2NF is better than 1NF; 3NF is better than 2NF For most business database design purposes, 3NF is as high as we need to go in normalization process Highest level of normalization is not always most desirable 25
26 Number of Tables Complexity Levels of Normalization Levels of normalization based on the amount of redundancy in the database. Various levels of normalization are: First Normal Form (1NF) Second Normal Form (2NF) Third Normal Form (3NF) Boyce-Codd Normal Form (BCNF) Fourth Normal Form (4NF) Fifth Normal Form (5NF) Domain Key Normal Form (DKNF) Redundancy Most databases should be 3NF or BCNF in order to avoid the database anomalies.
27 Levels of Normalization 1NF 2NF 3NF 4NF 5NF DKNF Each higher level is a subset of the lower level
28 Redundancy data redundancy in databases have a field repeated in two or more tables. However not all duplicated data is redundant. Foreign key fields will probably have duplicated values.
29 Redundancy why? Dealing with redundant data means that a company has to spend a lot of time, money and energy. Since, as mentioned, these redundant data are unknown to the organization, they can crawl into the system and give the system unwanted and unexpected results such as slowing down the entire system process, giving inaccurate data output and affecting data integrity very negatively. Redundant data can also create a risk to information quality if the different databases are not updated concurrently.
30 Redundancy why? Data redundancy is costly to address as it requires additional storage, synchronization between databases, and design work to align the information represented by different presentation of the same data. The problems associated with redundant data can be addressed by data normalization. Normalized tables generally can contain no redundant data because each attribute only appears in one table. Also, normalized tables do not contain derived data and instead, the data contained can be computed from existing attributes which has been selected as an expression based on the said attributes.
31 A worked example Normalisation
32 Table 1 Repeating groups Title Author1 Author 2 ISBN Subject Pages Publisher Database System Concepts Abraham Silberschatz Henry F. Korth MySQL, Computers 1168 McGraw-Hill Operating System Concepts Abraham Silberschatz Henry F. Korth Computers 944 McGraw-Hill Not Atomic
33 Table 1 problems This table is not very efficient with storage. This design does not protect data integrity. Third, this table does not scale well.
34 Conversion to First Normal Form Repeating group Derives its name from the fact that a group of multiple entries of same type can exist for any single key attribute occurrence. Relational table must not contain repeating groups. Normalizing table structure will reduce data redundancies. Normalization is three-step procedure 34
35 Conversion to First Normal Form (continued) Step 1: Eliminate the Repeating Groups Present data in tabular format, where each cell has single value and there are no repeating groups Eliminate repeating groups, eliminate nulls by making sure that each repeating group attribute contains an appropriate data value Make data atomic in the table. This means only 1 type of data in each attribute. Care needed here to ensure that atomicity is only applied when needed or logical to do so. 35
36 First Normal Form In our Table 1, we have two violations of First Normal Form: First, we have more than one author field, Second, our subject field contains more than one piece of information. With more than one value in a single field, it would be very difficult to search for all books on a given subject.
37 First Normal Table Table 2 Title Author ISBN Subject Pages Publisher Database System Concepts Database System Concepts Operating System Concepts Abraham Silberschatz MySQL 1168 McGraw-Hill Henry F. Korth Computers 1168 McGraw-Hill Henry F. Korth Computers 944 McGraw-Hill Operating System Concepts Abraham Silberschatz Computers 944 McGraw-Hill
38 Second Normal Table We now have two rows for a single book. But we would be violating the Second Normal Form A better solution to our problem would be to separate the data into separate tables- an Author table and a Subject table to store our information, removing that information from the Book table:
39 Conversion to First Normal Form (continued) Step 2: Identify the Primary Key Primary key must uniquely identify attribute value New key must be composed 39
40 Subject_ID Subject 1 MySQL 2 Computers Author_ID Last Name First Name 1 Silberschatz Abraham 2 Korth Henry ISBN Title Pages Publisher Database System Concepts Operating System Concepts 1168 McGraw-Hill 944 McGraw-Hill
41 Each table has a primary key, used for joining tables together when querying the data. A primary key value must be unique with in the table (no two books can have the same ISBN number), and a primary key is also an index, which speeds up data retrieval based on the primary key. Now to define relationships between the tables
42 Conversion to First Normal Form (continued) Step 3: Identify All Dependencies Dependencies can be depicted with help of a diagram Dependency diagram: Depicts all dependencies found within given table structure Helpful in getting bird s-eye view of all relationships among table s attributes Makes it less likely that will overlook an important dependency 42
43 Conversion to First Normal Form (continued) Step 3: Identify All Dependencies Functional dependency Title Author1 Author 2 ISBN Subject Pages Publisher Database System Concepts Abraham Silberschatz Henry F. Korth MySQL, Computers 1168 McGraw-Hill Operating System Concepts Abraham Silberschatz Henry F. Korth Computers 944 McGraw-Hill 43
44 Relationships ISBN Author_ID ISBN Subject_ID
45 Second Normal Form As the First Normal Form deals with redundancy of data across a horizontal row, Second Normal Form (or 2NF) deals with redundancy of data in vertical columns. As stated earlier, the normal forms are progressive, so to achieve Second Normal Form, the tables must already be in First Normal Form. The Book Table will be used for the 2NF example
46 2NF Table Publisher_ID Publisher Name 1 McGraw-Hill ISBN Title Pages Publisher_ID Database System Concepts Operating System Concepts
47 2NF Here we have a one-to-many relationship between the book table and the publisher. A book has only one publisher, and a publisher will publish many books. When we have a one-to-many relationship, we place a foreign key in the Book Table, pointing to the primary key of the Publisher Table. The other requirement for Second Normal Form is that you cannot have any data in a table with a composite key that does not relate to all portions of the composite key.
48 Third Normal Form Third normal form (3NF) requires that there are no functional dependencies of non-key attributes on something other than a candidate key. A table is in 3NF if all of the non-primary key attributes are mutually independent There should not be transitive dependencies
49 What is a transitive dependency? In Database Management System, a transitive dependency is a functional dependency which holds by virtue of transitivity. A transitive dependency can occur only in a relation that has three or more attributes. Let A, B, and C designate three distinct attributes (or distinct collections of attributes) in the relation. If C depends on B and B depends on A then C has transitive dependency i.e. it is functionally dependent on B (and not A the primary key). Think of a river with the left bank being A and the right bank being C. In the middle is a stepping stone (B). To get from C to A we would need B.
50 Boyce-Codd Normal Form BCNF requires that the table is 3NF and only determinants are the candidate keys.
51 The Boyce-Codd Normal Form (BCNF) Every determinant in table is a candidate key Has same characteristics as primary key, but for some reason, not chosen to be primary key When table contains only one candidate key, the 3NF and the BCNF are equivalent BCNF can be violated only when table contains more than one candidate key 51
52 The Boyce-Codd Normal Form (BCNF) (continued) Most designers consider the BCNF as special case of 3NF Table is in 3NF when it is in 2NF and there are no transitive dependencies Table can be in 3NF and fails to meet BCNF No partial dependencies, nor does it contain transitive dependencies A nonkey attribute is the determinant of a key attribute 52
53 Fourth Normal Form (4NF) Table is in fourth normal form (4NF) when both of the following are true: It is in 3NF Has no multiple sets of multivalued dependencies 4NF is largely academic if tables conform to following two rules: All attributes must be dependent on primary key, but independent of each other No row contains two or more multivalued facts about an entity 53
54 Denormalization Creation of normalized relations is important database design goal Processing requirements should also be a goal If tables decomposed to conform to normalization requirements: Number of database tables expands 54
55 Denormalization (continued) Joining the larger number of tables takes additional input/output (I/O) operations and processing logic, thereby reducing system speed Conflicts between design efficiency, information requirements, and processing speed are often resolved through compromises that may include denormalization 55
56 Denormalization (continued) Unnormalized tables in production database tend to suffer from these defects: Data updates are less efficient because programs that read and update tables must deal with larger tables Indexing is more cumbersome Unnormalized tables yield no simple strategies for creating virtual tables known as views 56
57 Denormalization (continued) Use denormalization cautiously Understand why under some circumstances unnormalized tables are better choice 57
58 What have we learnt today? Data analysis and design diagrams. Data flow diagrams. Dependency diagrams. Relationship degrees and Enterprise rules. Normalisation to 4NF. Denormalisation.
59 exercise Using the BasicData spreadsheet. Use the bottom up process on the customer data up to third normal form. This will form part of assignment 1.
Database Systems: Design, Implementation, and Management Tenth Edition. Chapter 6 Normalization of Database Tables
Database Systems: Design, Implementation, and Management Tenth Edition Chapter 6 Normalization of Database Tables Objectives In this chapter, students will learn: What normalization is and what role it
More informationDatabase Principles: Fundamentals of Design, Implementation, and Management Tenth Edition. Chapter 9 Normalizing Database Designs
Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition Chapter 9 Normalizing Database Designs NORMALIZATION What is normalization? Normalization is a procedure that is
More informationDatabase Tables and Normalization
Database Principles: Fundamentals of Design, Implementation, and Management Tenth Edition Chapter 9 Normalizing Database Designs (NORMALIZATION) MDM NUR RAZIA BINTI MOHD SURADI 019-3932846 razia@unisel.edu.my
More informationSteps in normalisation. Steps in normalisation 7/15/2014
Introduction to normalisation Normalisation Normalisation = a formal process for deciding which attributes should be grouped together in a relation Normalisation is the process of decomposing relations
More informationNormalisation Chapter2 Contents
Contents Objective... 64 Superkey & Candidate Keys... 65 Primary, Alternate and Foreign Keys... 65 Functional Dependence... 67 Using Instances... 70 Normalisation Introduction... 70 Normalisation Problems...
More informationNormalisation. Normalisation. Normalisation
Normalisation Normalisation Main objective in developing a logical data model for relational database systems is to create an accurate and efficient representation of the data, its relationships, and constraints
More informationIS 263 Database Concepts
IS 263 Database Concepts Lecture 4: Normalization Instructor: Henry Kalisti 1 Department of Computer Science and Engineering Limitations of E- R Designs Provides a set of guidelines, does not result in
More informationDatabase Systems. Normalization Lecture# 7
Database Systems Normalization Lecture# 7 Lecture 7: Normalization Normalization (Brief Overview) Functional Dependencies and Keys 1 st Normal Form 2 nd Normal Form 3 rd Normal Form Class Activity 3 Normalization
More informationThe strategy for achieving a good design is to decompose a badly designed relation appropriately.
The strategy for achieving a good design is to decompose a badly designed relation appropriately. Functional Dependencies The single most important concept in relational schema design theory is that of
More informationACS-2914 Normalization March 2009 NORMALIZATION 2. Ron McFadyen 1. Normalization 3. De-normalization 3
NORMALIZATION 2 Normalization 3 De-normalization 3 Functional Dependencies 4 Generating functional dependency maps from database design maps 5 Anomalies 8 Partial Functional Dependencies 10 Transitive
More informationTHE RELATIONAL DATABASE MODEL
THE RELATIONAL DATABASE MODEL Introduction to relational DB Basic Objects of relational model Properties of relation Representation of ER model to relation Keys Relational Integrity Rules Functional Dependencies
More informationپوهنتون کابل پوهنحی كمپيوترساینس پوهنیار محمد شعیب "زرین خیل"
پوهنتون کابل پوهنحی كمپيوترساینس : : تهیه کننده سال پوهنیار محمد شعیب "زرین خیل" 1389 Introduction to Database and Data Models - Relational Model 08 By: M Shuaib Zarinkhail 2010 Referential Integrity Constraint
More informationHow to design a database
Chapter 16 How to design a database A database system is modeled after a real-word system 2017, Mike Murach & Associates, Inc. C 16, Slide 1 2017, Mike Murach & Associates, Inc. C 16, Slide 4 Objectives
More informationCSCI 403: Databases 13 - Functional Dependencies and Normalization
CSCI 403: Databases 13 - Functional Dependencies and Normalization Introduction The point of this lecture material is to discuss some objective measures of the goodness of a database schema. The method
More informationNormalization. VI. Normalization of Database Tables. Need for Normalization. Normalization Process. Review of Functional Dependence Concepts
VI. Normalization of Database Tables Normalization Evaluating and correcting relational schema designs to minimize data redundancies Reduces data anomalies Assigns attributes to tables based on functional
More informationThe Relational Model and Normalization
The Relational Model and Normalization 1. Introduction 2 2. Relational Model Terminology 3 4. Normal Forms 11 5. Multi-valued Dependency 21 6. The Fifth Normal Form 22 The Relational Model and Normalization
More information8) A top-to-bottom relationship among the items in a database is established by a
MULTIPLE CHOICE QUESTIONS IN DBMS (unit-1 to unit-4) 1) ER model is used in phase a) conceptual database b) schema refinement c) physical refinement d) applications and security 2) The ER model is relevant
More informationDatabase Foundations. 3-9 Validating Data Using Normalization. Copyright 2015, Oracle and/or its affiliates. All rights reserved.
Database Foundations 3-9 Roadmap Conceptual and Physical Data Models Business Rules Entities Attributes Unique Identifiers Relationships Validating Relationships Tracking Data Changes over Time Validating
More informationIn This Lecture. Normalisation to BCNF. Lossless decomposition. Normalisation so Far. Relational algebra reminder: product
In This Lecture Normalisation to BCNF Database Systems Lecture 12 Natasha Alechina More normalisation Brief review of relational algebra Lossless decomposition Boyce-Codd normal form (BCNF) Higher normal
More informationDatabase Management System Prof. Partha Pratim Das Department of Computer Science & Engineering Indian Institute of Technology, Kharagpur
Database Management System Prof. Partha Pratim Das Department of Computer Science & Engineering Indian Institute of Technology, Kharagpur Lecture - 19 Relational Database Design (Contd.) Welcome to module
More informationLogical Database Design Normalization
Chapter Four Logical Database Design Normalization Objectives Recalling Relational concepts Understand different anomalies and functional dependency concepts Use normalization to convert anomalous tables
More informationTest Bank For A Guide To Mysql 1st Edition By Pratt And Last
Test Bank For A Guide To Mysql 1st Edition By Pratt And Last Link full download test bank: https://digitalcontentmarket.org/download/test-bank-for-a-guide-to-mysql-1st-edition-bypratt-and-last/ Link full
More informationLink download full of Solution Manual:
Test Bank for A Guide to MySQL 1st Edition by Pratt and Last Link download full: http://testbankair.com/download/test-bank-for-a-guide-to-mysql-1st-edition-by-prattand-last/ Link download full of Solution
More informationDatabase Normalization. (Olav Dæhli 2018)
Database Normalization (Olav Dæhli 2018) 1 What is normalization and why normalize? Normalization: A set of rules to decompose relations (tables) into smaller relations (tables), without loosing any data
More informationUNIT 3 DATABASE DESIGN
UNIT 3 DATABASE DESIGN Objective To study design guidelines for relational databases. To know about Functional dependencies. To have an understanding on First, Second, Third Normal forms To study about
More informationInstitute of Southern Punjab, Multan
Institute of Southern Punjab, Multan Mr. Muhammad Nouman Farooq BSC-H (Computer Science) MS (Telecomm. and Networks) Honors: Magna Cumm Laude Honors Degree Gold Medalist! Blog Url: noumanfarooqatisp.wordpress.com
More informationCopyright 2016 Ramez Elmasri and Shamkant B. Navathe
CHAPTER 14 Basics of Functional Dependencies and Normalization for Relational Databases Slide 14-2 Chapter Outline 1 Informal Design Guidelines for Relational Databases 1.1 Semantics of the Relation Attributes
More informationUnit 2. Unit 3. Unit 4
Course Objectives At the end of the course the student will be able to: 1. Differentiate database systems from traditional file systems by enumerating the features provided by database systems.. 2. Design
More informationCS211 Lecture: Database Design
CS211 Lecture: Database Design Objectives: last revised November 21, 2006 1. To introduce the anomalies that result from redundant storage of data 2. To introduce the notion of functional dependencies
More information15CS53: DATABASE MANAGEMENT SYSTEM
15CS53: DATABASE MANAGEMENT SYSTEM Subject Code: 15CS53 I.A. Marks: 20 Hours/Week: 04 Exam Hours: 03 Total Hours: 56 Exam Marks: 80 Objectives of the Course: This course will enable students to Provide
More informationFIT1004 Database Topic 6: Normalisation
FIT1004 Database Topic 6: Normalisation Learning Objectives: Understand the purpose of normalisation Understand the problems associated with redundant data Identify various types of update anomalies such
More informationDATABASE MANAGEMENT SYSTEM SHORT QUESTIONS. QUESTION 1: What is database?
DATABASE MANAGEMENT SYSTEM SHORT QUESTIONS Complete book short Answer Question.. QUESTION 1: What is database? A database is a logically coherent collection of data with some inherent meaning, representing
More informationTest Bank for A Guide to SQL 9th Edition by Pratt
Test Bank for A Guide to SQL 9th Edition by Pratt Link full download: https://testbankservice.com/download/test-bank-for-a-guideto-sql-9th-edition-by-pratt Chapter 2: Database Design Fundamentals True
More informationInformal Design Guidelines for Relational Databases
Outline Informal Design Guidelines for Relational Databases Semantics of the Relation Attributes Redundant Information in Tuples and Update Anomalies Null Values in Tuples Spurious Tuples Functional Dependencies
More informationRedundancy:Dependencies between attributes within a relation cause redundancy.
Normalization Normalization: It is the process of removing redundant data from your tables in order to improve storage efficiency, data integrity and scalability. This improvement is balanced against an
More informationApplied Databases. Sebastian Maneth. Lecture 5 ER Model, Normal Forms. University of Edinburgh - January 30 th, 2017
Applied Databases Lecture 5 ER Model, Normal Forms Sebastian Maneth University of Edinburgh - January 30 th, 2017 Outline 2 1. Entity Relationship Model 2. Normal Forms From Last Lecture 3 the Lecturer
More informationUFCEKG : Dt Data, Schemas Sh and Applications. Lecture 10 Database Theory & Practice (4) : Data Normalization
UFCEKG 20 2 2 : Dt Data, Schemas Sh and Applications Lecture 10 Database Theory & Practice (4) : Data Normalization Normalization (1) o What is Normalization? Informally, Normalization can be thought of
More informationCMP-3440 Database Systems
CMP-3440 Database Systems Logical Design Lecture 03 zain 1 Database Design Process Application 1 Conceptual requirements Application 1 External Model Application 2 Application 3 Application 4 External
More informationDatabases The theory of relational database design Lectures for m
Databases The theory of relational database design Lectures for mathematics students April 2, 2017 General introduction Look; that s why there s rules, understand? So that you think before you break em.
More informationApplied Databases. Sebastian Maneth. Lecture 5 ER Model, normal forms. University of Edinburgh - January 25 th, 2016
Applied Databases Lecture 5 ER Model, normal forms Sebastian Maneth University of Edinburgh - January 25 th, 2016 Outline 2 1. Entity Relationship Model 2. Normal Forms Keys and Superkeys 3 Superkey =
More informationNormalization. Un Normalized Form (UNF) Share. Download the pdf version of these notes.
Normalization Share Download the pdf version of these notes. While designing a database out of an entity relationship model, the main problem existing in that raw database is redundancy. Redundancy is
More informationComputer Science 597A Fall 2008 First Take-home Exam Out: 4:20PM Monday November 10, 2008 Due: 3:00PM SHARP Wednesday, November 12, 2008
Computer Science 597A Fall 2008 First Take-home Exam Out: 4:20PM Monday November 10, 2008 Due: 3:00PM SHARP Wednesday, November 12, 2008 Instructions: This exam must be entirely your own work. Do not consult
More informationData and Knowledge Management Dr. Rick Jerz
Data and Knowledge Management Dr. Rick Jerz 1 Goals Define big data and discuss its basic characteristics Understand ways to store information Understand the value of a Database Management System Explain
More informationDistributed Database Systems By Syed Bakhtawar Shah Abid Lecturer in Computer Science
Distributed Database Systems By Syed Bakhtawar Shah Abid Lecturer in Computer Science 1 Distributed Database Systems Basic concepts and Definitions Data Collection of facts and figures concerning an object
More informationChapter 10. Normalization. Chapter Outline. Chapter Outline(contd.)
Chapter 10 Normalization Chapter Outline 1 Informal Design Guidelines for Relational Databases 1.1Semantics of the Relation Attributes 1.2 Redundant Information in Tuples and Update Anomalies 1.3 Null
More informationNormalization in DBMS
Unit 4: Normalization 4.1. Need of Normalization (Consequences of Bad Design-Insert, Update & Delete Anomalies) 4.2. Normalization 4.2.1. First Normal Form 4.2.2. Second Normal Form 4.2.3. Third Normal
More informationNormalization Rule. First Normal Form (1NF) Normalization rule are divided into following normal form. 1. First Normal Form. 2. Second Normal Form
Normalization Rule Normalization rule are divided into following normal form. 1. First Normal Form 2. Second Normal Form 3. Third Normal Form 4. BCNF First Normal Form (1NF) As per First Normal Form, no
More information1. The process of determining the particular tables and columns that will comprise a database is known as database design.
True / False 1. The process of determining the particular tables and columns that will comprise a database is known as database design. REFERENCES: 21 2. A tabular database is a collection of tables. REFERENCES:
More informationUnit- III (Functional dependencies and Normalization, Relational Data Model and Relational Algebra)
Unit- III (Functional dependencies and Normalization, Relational Data Model and Relational Algebra) Important questions Section A :(2 Marks) 1.What is Functional Dependency? Functional dependency (FD)
More informationRelational Database design. Slides By: Shree Jaswal
Relational Database design Slides By: Shree Jaswal Topics: Design guidelines for relational schema, Functional Dependencies, Definition of Normal Forms- 1NF, 2NF, 3NF, BCNF, Converting Relational Schema
More informationData and Knowledge Management. Goals. Big Data. Dr. Rick Jerz
Data and Knowledge Management Dr. Rick Jerz 1 Goals Define big data and discuss its basic characteristics Understand ways to store information Understand the value of a Database Management System Explain
More informationch02 True/False Indicate whether the statement is true or false.
ch02 True/False Indicate whether the statement is true or false. 1. The process of determining the particular tables and columns that will comprise a database is known as database design. 2. A tabular
More informationChapter 14 Outline. Normalization for Relational Databases: Outline. Chapter 14: Basics of Functional Dependencies and
Ramez Elmasri, Shamkant B. Navathe(2016) Fundamentals of Database Systems (7th Edition), pearson, isbn 10: 0-13-397077-9;isbn-13:978-0-13-397077-7. Chapter 14: Basics of Functional Dependencies and Normalization
More informationData analysis and design Unit number: 23 Level: 5 Credit value: 15 Guided learning hours: 60 Unit reference number: H/601/1991.
Unit title: Data analysis and design Unit number: 23 Level: 5 Credit value: 15 Guided learning hours: 60 Unit reference number: H/601/1991 UNIT AIM AND PURPOSE The aim of this unit is to equip learners
More informationDATABASE MANAGEMENT SYSTEM SUBJECT CODE: CE 305
DATABASE MANAGEMENT SYSTEM SUBJECT CODE: CE 305 Teaching Scheme (Credits and Hours) Teaching scheme Total Evaluation Scheme L T P Total Credit Theory Mid Sem Exam CIA Pract. Total Hrs Hrs Hrs Hrs Hrs Marks
More informationElmasri/Navathe, Fundamentals of Database Systems, Fourth Edition Chapter 10-2
Elmasri/Navathe, Fundamentals of Database Systems, Fourth Edition Chapter 10-2 Chapter Outline 1 Informal Design Guidelines for Relational Databases 1.1Semantics of the Relation Attributes 1.2 Redundant
More informationChapter 14. Database Design Theory: Introduction to Normalization Using Functional and Multivalued Dependencies
Chapter 14 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
More informationNormalization is based on the concept of functional dependency. A functional dependency is a type of relationship between attributes.
Lecture Handout Database Management System Lecture No. 19 Reading Material Database Systems Principles, Design and Implementation written by Catherine Ricardo, Maxwell Macmillan. Section 7.1 7.7 Database
More informationChapter 6: Relational Database Design
Chapter 6: Relational Database Design Chapter 6: Relational Database Design Features of Good Relational Design Atomic Domains and First Normal Form Decomposition Using Functional Dependencies Second Normal
More informationitxperts shivpuri Page No. 1 Normalization
www.itxperts.co.in itxperts shivpuri Page No. 1 Normalization While designing a database out of an entity relationship model, the main problem existing in that raw database is redundancy. Redundancy is
More informationDatabase Design Theory and Normalization. CS 377: Database Systems
Database Design Theory and Normalization CS 377: Database Systems Recap: What Has Been Covered Lectures 1-2: Database Overview & Concepts Lecture 4: Representational Model (Relational Model) & Mapping
More informationData about data is database Select correct option: True False Partially True None of the Above
Within a table, each primary key value. is a minimal super key is always the first field in each table must be numeric must be unique Foreign Key is A field in a table that matches a key field in another
More informationChapter 10. Chapter Outline. Chapter Outline. 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 informationDatabases. Dr. Richard E. Turner March 5, 2013
Databases Dr. Richard E. Turner (ret26@cam.ac.uk) March 5, 2013 Big-data: Databases Database = structured collection of data Everywhere: Facebook, MySpace, Google, Android (sqlite3), Amazon,... Amazon
More informationDBMS Chapter Three IS304. Database Normalization-Comp.
Database Normalization-Comp. Contents 4. Boyce Codd Normal Form (BCNF) 5. Fourth Normal Form (4NF) 6. Fifth Normal Form (5NF) 7. Sixth Normal Form (6NF) 1 4. Boyce Codd Normal Form (BCNF) In the first
More informationSWEN-220 Mathematical Models of Software
SWEN-220 Mathematical Models of Software Normalization 1 Well Structured Relations Contain minimal redundancy (data duplication). Allow users to insert, delete and modify data without anomalies errors
More informationA7-R3: INTRODUCTION TO DATABASE MANAGEMENT SYSTEMS
A7-R3: INTRODUCTION TO DATABASE MANAGEMENT SYSTEMS NOTE: 1. There are TWO PARTS in this Module/Paper. PART ONE contains FOUR questions and PART TWO contains FIVE questions. 2. PART ONE is to be answered
More informationToday Learning outcomes LO2
2015 2016 Phil Smith Today Learning outcomes LO2 On successful completion of this unit you will: 1. Be able to design and implement relational database systems. 2. Requirements. 3. User Interface. I am
More informationNormalization. Normal Forms. Normal Forms
Normalization A technique that organizes data attributes (or fields) such that they are grouped to form stable, flexible and adaptive entities. 5- Normal Forms First Normal Form (NF) There are no attributes
More informationFunctional Dependencies and. Databases. 1 Informal Design Guidelines for Relational Databases. 4 General Normal Form Definitions (For Multiple Keys)
1 / 13 1 Informal Design Guidelines for Relational Databases 1.1Semantics of the Relation Attributes 1.2 Redundant d Information in Tuples and Update Anomalies 1.3 Null Values in Tuples 1.4 Spurious Tuples
More informationIntroduction to Databases, Fall 2003 IT University of Copenhagen. Lecture 4: Normalization. September 16, Lecturer: Rasmus Pagh
Introduction to Databases, Fall 2003 IT University of Copenhagen Lecture 4: Normalization September 16, 2003 Lecturer: Rasmus Pagh Today s lecture What you should remember from previously. Anomalies in
More informationCTL.SC4x Technology and Systems
in Supply Chain Management CTL.SC4x Technology and Systems Key Concepts Document This document contains the Key Concepts for the SC4x course, Weeks 1 and 2. These are meant to complement, not replace,
More informationCS403- Database Management Systems Solved MCQS From Midterm Papers. CS403- Database Management Systems MIDTERM EXAMINATION - Spring 2010
CS403- Database Management Systems Solved MCQS From Midterm Papers April 29,2012 MC100401285 Moaaz.pk@gmail.com Mc100401285@gmail.com PSMD01 CS403- Database Management Systems MIDTERM EXAMINATION - Spring
More informationIntroduction to Database Design, fall 2011 IT University of Copenhagen. Normalization. Rasmus Pagh
Introduction to Database Design, fall 2011 IT University of Copenhagen Normalization Rasmus Pagh Based on KBL sections 6.1-6.8 (except p. 203 207m), 6.9 (until Multivalued dependencies ), 6.11, and 6.12.
More informationDetailed Data Modelling. Detailed Data Modelling. Detailed Data Modelling. Identifying Attributes. Attributes
IMS1002 /CSE1205 Systems Analysis and Design Detailed Data Modelling The objective of detailed data modelling is to develop a detailed data structure that: Detailed Data Modelling: Attribute Collection
More informationLecture 3. Wednesday, September 3, 2014
Lecture 3 Wednesday, September 3, 2014 ER Diagrams Last week, we covered ER diagrams which allow us to show entities, attributes, and relationships The last component of an ER diagram is the cardinality
More informationChapter 3B Objectives. Relational Set Operators. Relational Set Operators. Relational Algebra Operations
Chapter 3B Objectives Relational Set Operators Learn About relational database operators SELECT & DIFFERENCE PROJECT & JOIN UNION PRODUCT INTERSECT DIVIDE The Database Meta Objects the data dictionary
More informationcustomer = (customer_id, _ customer_name, customer_street,
Relational Database Design COMPILED BY: RITURAJ JAIN The Banking Schema branch = (branch_name, branch_city, assets) customer = (customer_id, _ customer_name, customer_street, customer_city) account = (account_number,
More informationRelational Database Design (II)
Relational Database Design (II) 1 Roadmap of This Lecture Algorithms for Functional Dependencies (cont d) Decomposition Using Multi-valued Dependencies More Normal Form Database-Design Process Modeling
More informationLecture 5 STRUCTURED ANALYSIS. PB007 So(ware Engineering I Faculty of Informa:cs, Masaryk University Fall Bühnová, Sochor, Ráček
Lecture 5 STRUCTURED ANALYSIS PB007 So(ware Engineering I Faculty of Informa:cs, Masaryk University Fall 2015 1 Outline ² Yourdon Modern Structured Analysis (YMSA) Context diagram (CD) Data flow diagram
More informationData Modeling, Normalization and Denormalisation
PGCONF.EU 2018, LISBON OCTOBER 24, 2018 Data Modeling, Normalization and Denormalisation Dimitri Fontaine Citus Data POSTGRESQL MAJOR CONTRIBUTOR PostgreSQL CURRENTLY WORKING AT Citus Data https://masteringpostgresql.com
More informationDetailed Data Modelling: Attribute Collection and Normalisation of Data
Detailed Data Modelling IMS1002 /CSE1205 Systems Analysis and Design Detailed Data Modelling: Attribute Collection and Normalisation of Data The objective of detailed data modelling is to develop a detailed
More informationSchema And Draw The Dependency Diagram
Given That Information Write The Relational Schema And Draw The Dependency Diagram below, write the relational schema, draw its dependency diagram, and identify all You can assume that any given product
More informationNormalization. Murali Mani. What and Why Normalization? To remove potential redundancy in design
1 Normalization What and Why Normalization? To remove potential redundancy in design Redundancy causes several anomalies: insert, delete and update Normalization uses concept of dependencies Functional
More informationDr. Anis Koubaa. Advanced Databases SE487. Prince Sultan University
Advanced Databases Prince Sultan University College of Computer and Information Sciences Fall 2013 Chapter 15 Basics of Functional Dependencies and Normalization for Relational Databases Anis Koubaa SE487
More informationLecture 11 - Chapter 8 Relational Database Design Part 1
CMSC 461, Database Management Systems Spring 2018 Lecture 11 - Chapter 8 Relational Database Design Part 1 These slides are based on Database System Concepts 6th edition book and are a modified version
More informationDatabase Normalization Complete
Database Normalization Complete Table Of Contents Part 1 - Introduction 1.1 What is Normalization? 1.2 Why should I Normalize? 1.3 Terminology 1.4 Summary JasonM (jasonm@accessvba.com) Last Updated: 28
More information6.830 Lecture PS1 Due Next Time (Tuesday!) Lab 1 Out end of week start early!
6.830 Lecture 3 9.13.2017 PS1 Due Next Time (Tuesday!) Lab 1 Out end of week start early! Relational Model Continued, and Schema Design and Normalization Animals(name,age,species,cageno,keptby,feedtime)
More informationCase Study: Lufthansa Cargo Database
Case Study: Lufthansa Cargo Database Carsten Schürmann 1 Today s lecture More on data modelling Introduction to Lufthansa Cargo Database Entity Relationship diagram Boyce-Codd normal form 2 From Lecture
More informationHow to speed up a database which has gotten slow
Triad Area, NC USA E-mail: info@geniusone.com Web: http://geniusone.com How to speed up a database which has gotten slow hardware OS database parameters Blob fields Indices table design / table contents
More informationNormalization Normalization
Normalization Normalization We discuss four normal forms: first, second, third, and Boyce-Codd normal forms 1NF, 2NF, 3NF, and BCNF Normalization is a process that improves a database design by generating
More informationRelational Design: Characteristics of Well-designed DB
1. Minimal duplication Relational Design: Characteristics of Well-designed DB Consider table newfaculty (Result of F aculty T each Course) Id Lname Off Bldg Phone Salary Numb Dept Lvl MaxSz 20000 Cotts
More informationDatabases 1. Daniel POP
Databases 1 Daniel POP Week 6 & 7 Agenda Introduction to normalization Functional dependencies 1NF 2NF 3NF. Transitive dependencies BCNF 4NF. Multivalued dependencies 5NF De-normalization Normalization
More information7) To be considered a composite key, a key must contain at least two attributes. Answer: TRUE
Database Concepts, 7e (Kroenke/Auer) Chapter 2 The Relational Model 1) While the relational model for databases appears to hold much promise, few commercial databases have implemented it. Diff: 1 Page
More informationLecture 4. Database design IV. INDs and 4NF Design wrapup
Lecture 4 Database design IV INDs and 4NF Design wrapup Problem description We want a database that we can use for scheduling courses and lectures. This is how it s supposed to work: code name Course dept
More informationDatabase Systems: Design, Implementation, and Management Tenth Edition. Chapter 4 Entity Relationship (ER) Modeling
Database Systems: Design, Implementation, and Management Tenth Edition Chapter 4 Entity Relationship (ER) Modeling Objectives In this chapter, students will learn: The main characteristics of entity relationship
More informationChapter 2 Introduction to Relational Models
CMSC 461, Database Management Systems Spring 2018 Chapter 2 Introduction to Relational Models These slides are based on Database System Concepts book and slides, 6th edition, and the 2009 CMSC 461 slides
More informationCS411 Database Systems. 05: Relational Schema Design Ch , except and
CS411 Database Systems 05: Relational Schema Design Ch. 3.1-3.5, except 3.4.2-3.4.3 and 3.5.3. 1 How does this fit in? ER Diagrams: Data Definition Translation to Relational Schema: Data Definition Relational
More informationLogical database design
Databases 2013 2014/Ia Homework 2 Due date: September 27, 2013 Logical database design This homework consists of two parts. In the first part of this homework, we will go through some of the design decisions
More informationModern Systems Analysis and Design
Modern Systems Analysis and Design Sixth Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Designing Databases Learning Objectives Concisely define each of the following key database design terms:
More information