Athabasca University Under Development for COMP 200 Gary Novokowsky

Slides:



Advertisements
Similar presentations
Normalization Rules for Database Tables
Advertisements

Relational Terminology. Normalization A method where data items are grouped together to better accommodate business changes Provides a method for representing.
Normalization What is it?
Normalisation Ensuring data integrity in database design 1.
ACCESS PART 2. Objectives Database Tables Table Parts Key Field Query and Reports Import from Excel Link to Excel.
Database Design Conceptual –identify important entities and relationships –determine attribute domains and candidate keys –draw the E-R diagram Logical.
Boyce-Codd Normal Form Kelvin Nishikawa SE157a-03 Fall 2006 Kelvin Nishikawa SE157a-03 Fall 2006.
Designing a Database Unleashing the Power of Relational Database Design.
1 NORMALISATION. 2 Introduction Overview Objectives Intro. to Subject Why we normalise 1, 2 & 3 NF Normalisation Process Example Summary.
WELL-DESIGNED DATABASES Process faster Easy to develop and maintain Easy to read and write code.
Relational Data Analysis II. Plan Introduction Structured Methods –Data Flow Modelling –Data Modelling –Relational Data Analysis Feasibility Maintenance.
Project and Data Management Software
Normalization A337. A337 - Reed Smith2 Structure What is a database? ◦ Tables of information  Rows are referred to as records  Columns are referred.
System Analysis and Design
Bad DB Design Duplicate of data Duplicate of data Updating Updating Deleting Deleting.
Page 1 ISMT E-120 Introduction to Microsoft Access & Relational Databases The Influence of Software and Hardware Technologies on Business Productivity.
Database Design.  Define a table for each entity  Give the table the same name as the entity  Make the primary key the same as the identifier of the.
Page 1 ISMT E-120 Desktop Applications for Managers Introduction to Microsoft Access.
The Relational Database Model CST272. Return Creating the Unnormalized Table n List the fields n Select a primary key – The field (or concatenation of.
Normalization Rules for Database Tables Northern Arizona University College of Business Administration.
Normalization.
CREATE THE DIFFERENCE Normalisation (special thanks to Janet Francis for this presentation)
SQL Normalization Database Design Lecture 5. Copyright 2006Page 2 SQL Normalization Database Design 1 st Normal Form 1 st Normal Form 2 nd Normal Form.
1 Class Agenda (04/09 through 04/16)  Review HW #8  Present normalization process Enhance conceptual knowledge of database design. Improve practical.
Relational databases and third normal form As always click on speaker notes under view when executing to get more information!
CTFS Workshop Shameema Esufali Suzanne Lao Data coordinators and technical resources for the network
Normalization A technique that organizes data attributes (or fields) such that they are grouped to form stable, flexible and adaptive entities.
Module Title? DBMS Normalization. Module Title? DBMS Normalization  Normalization is the process of removing redundant data from tables in order to improve.
A Normalisation Example Mark Kelly McKinnon Secondary College Vceit.com Based on work by Robert Timmer-Arends.
The Relational Model and Normalization R. Nakatsu.
Normalization (Codd, 1972) Practical Information For Real World Database Design.
Copyright Ó Oracle Corporation, All rights reserved. Normalization Use the student note section below for further explanation of the slide content.Use.
CORE 2: Information systems and Databases NORMALISING DATABASES.
MS Access: Creating Relational Databases Instructor: Vicki Weidler Assistant: Joaquin Obieta.
Data Models and Relational Databases Chapter 2. Learning Objectives Identify primary and foreign keys for each entity and relevant relationships in the.
Normalization Information Systems II Ioan Despi. Informal approach Building a database structure : A process of examining the data which is useful & necessary.
Normalization Well structured relations and anomalies Normalization First normal form (1NF) Functional dependence Partial functional dependency Second.
Customer Order Order Number Date Cust ID Last Name First Name State Amount Tax Rate Product 1 ID Product 1 Description Product 1 Quantity Product 2 ID.
Unit 4 Normalisationand Relational Database Management Systems.
Normalization Data Design - Mr. Ahmad Al-Ghoul
A337 - Reed Smith1 Structure What is a database? –Table of information Rows are referred to as records Columns are referred to as fields Record identifier.
Creating Databases Data normalization. Integrity and Robustness. Work session. Homework: Prepare short presentation on enhancement projects. Continue working.
Normalization. 2 u Main objective in developing a logical data model for relational database systems is to create an accurate representation of the data,
Normalization MIS335 Database Systems. Why Normalization? Optimizing database structure Removing duplications Accelerating the instructions Data integrity!
Chapter 56 Relational Database Design Compiled by Eddie Moorcroft.
CTFS Workshop Shameema Esufali Asian data coordinator and technical resource for the network
NORMALIZATION. What is Normalization  The process of effectively organizing data in a database  Two goals  To eliminate redundant data  Ensure data.
* Database is a group of related objects * Objects can be Tables, Forms, Queries or Reports * All data reside in Tables * A Row in a Table is a record.
Understand Relational Database Management Systems Software Development Fundamentals LESSON 6.1.
Postgresql East Philadelphia, PA Databases – A Historical Perspective.
Sample Table Standard Notation Entity name in uppercase
Microsoft Access 2010 Chapter 11 Database Design.
Databases Database Normalisation. Learning Objectives Design simple relational databases to the third normal form (3NF).
NormalisationNormalisation Normalization is the technique of organizing data elements into records. Normalization is the technique of organizing data elements.
NORMALIZATION Handout - 4 DBMS. What is Normalization? The process of grouping data elements into tables in a way that simplifies retrieval, reduces data.
Logical Database Design and Relational Data Model Muhammad Nasir
What Is Normalization  In relational database design, the process of organizing data to minimize redundancy  Usually involves dividing a database into.
Starter Draw a mind map for topic 6 Databases. Objectives Revise topic CG3.6 Databases using various activities and ensure that topics covered are understood.
Normalisation FORM RULES 1NF 2NF 3NF. What is normalisation of data? The process of Normalisation organises your database to: Reduce or minimise redundant.
Normalisation Worked example for an Order Remember : The data should depend upon the key, the whole key and nothing but the key.
NORMALISATION OF DATABASES. WHAT IS NORMALISATION? Normalisation is used because Databases need to avoid have redundant data, which makes it inefficient.
Announcements n Difference between “excused” and “absent” n Office hours next week May not be here Monday Tuesday: 1:00 to 2:00 Wednesday: 10:00 to 11:00.
Flat file and relational databases Flat file database In a flat file database information is held in a single table. Student IDStudent name GenderDOBCourse.
SEEM3430: Information Systems Analysis and Design
© 2011 Pearson Education, Inc. Publishing as Prentice Hall
Normalization Referential Integrity
Entity relationship diagrams
Database Normalisation
System Analysis and Design
Normalisation Un-normalised Data (UNF or 0NF) Data Attributes:
Presentation transcript:

Athabasca University Under Development for COMP 200 Gary Novokowsky Data Normalization Athabasca University Under Development for COMP 200 Gary Novokowsky Gary Novokowsky, Athabasca University

Gary Novokowsky, Athabasca University Non-Normalized Data Contains duplicate non-key items Notice how the table on the next slide (broken to fit on a slide), contains duplicate data in almost every single column of the table. Gary Novokowsky, Athabasca University

Non-Normalized Student Data Gary Novokowsky, Athabasca University

Gary Novokowsky, Athabasca University 1NF – First Normal Form First remove repeated fields. Accomplish this by breaking the original table into two separate tables. Note how the first table on the following page has the repeating fields removed. The second table has a concatenated key. Although items repeat in the first two columns, they never repeat when combined. Even though they are two separate columns, you may think of them as a single column because when combined they form a single, unique key. Although the Course Name field contains repeating fields notice how it is never associated with the same key. This is because the concatenated (or combined) key is unique for each row that contains duplicate data in the Course Name field. Gary Novokowsky, Athabasca University

Gary Novokowsky, Athabasca University 1NF – First Normal Form Key = STUDENT ID # Both STUDENT ID # and COURSE # are foreign keys and together form a concatenated key Although “Data Structures” is repeated in the Course Name column, one instance is associated with the key 343567, COMP 272 and one is associated with the key 444765, COMP 272, different concatenated keys. Gary Novokowsky, Athabasca University

Gary Novokowsky, Athabasca University 2NF – Second Normal Form Ensure all non-key attributes (data items), are identified by the full key. I.E., there should be no components in a concatenated key that are not required to uniquely identify the data items. The Course table from the previous slide contains a Course # field which identifies the Course Name, but Course Name does not require the Student # part of the concatenated key for identification. We now split the Course table into two tables (Course table and Grade table) to arrive at 2NF as shown in the next slide. Gary Novokowsky, Athabasca University

Gary Novokowsky, Athabasca University 2NF – Second Normal Form Grades has a concatenated key made up of two foreign keys. Course # remains the key for this table. Gary Novokowsky, Athabasca University

Gary Novokowsky, Athabasca University 3NF – Third Normal Form Ensure all non-key attributes (data items), are independent of other non-key attributes in the table. An examination of our tables shows this is a problem in the Student-Programme table because the Programme Name and Programme Description fields are dependent on Programme # field. Resolve this issue by splitting the first table into two tables – the Student table and the Programme table. Note how the key field from the Programme table, Programme #, must remain as part of the Student table in order to form a link between the two tables. If this field were to be left out there would be no relationship between the Programme table and the rest of the database tables. Gary Novokowsky, Athabasca University

Gary Novokowsky, Athabasca University 3NF – Third Normal Form Gary Novokowsky, Athabasca University