CORE 2: Information systems and Databases NORMALISING DATABASES.

Slides:



Advertisements
Similar presentations
CHAPTER OBJECTIVE: NORMALIZATION THE SNOWFLAKE SCHEMA.
Advertisements

Relational Terminology. Normalization A method where data items are grouped together to better accommodate business changes Provides a method for representing.
Topic Database Normalisation S McKeever Advanced Databases 1.
Normalisation Ensuring data integrity in database design 1.
Athabasca University Under Development for COMP 200 Gary Novokowsky
Topic Denormalisation S McKeever Advanced Databases 1.
Class Presentation: Normal Form By Wen Ying Gao CS157A Section 2 October 20, 2005.
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.
Understand Normalization
Project and Data Management Software
Chapter 4 Relational Databases Copyright © 2012 Pearson Education, Inc. publishing as Prentice Hall 4-1.
Terms - data,information, file record, table, row, column, transaction, concurrency Concepts - data integrity, data redundancy, Type of databases – single-user,
Chapter 4 Relational Databases Copyright © 2012 Pearson Education 4-1.
Normalization Quiz Tao Li Grant Horntvedt. 1. Which of the following statements is true: a. Normal forms can be derived by inspecting the data in various.
Introduction to Schema Refinement. Different problems may arise when converting a relation into standard form They are Data redundancy Update Anomalies.
Week 6 Lecture Normalization
Modelling Techniques - Normalisation Description and exemplification of normalisation.Description and exemplification of normalisation. Creation of un-normalised.
CREATE THE DIFFERENCE Normalisation (special thanks to Janet Francis for this presentation)
1 © Prentice Hall, 2002 Physical Database Design Dr. Bijoy Bordoloi.
Cambridge TEC - Level 3 Certificate/Diploma IT. ICT Dept ScenarioLO1LO2LO3.
Chapter 1 Overview of Database Concepts Oracle 10g: SQL
Concepts and Terminology Introduction to Database.
Normalization A technique that organizes data attributes (or fields) such that they are grouped to form stable, flexible and adaptive entities.
Concepts of Database Management, Fifth Edition
Module III: The Normal Forms. Edgar F. Codd first proposed the process of normalization and what came to be known as the 1st normal form. The database.
SALINI SUDESH. Primarily a tool to validate and improve a logical design so that it satisfies certain constraints that avoid unnecessary duplication of.
Chapter 7 1 Database Principles Data Normalization Primarily a tool to validate and improve a logical design so that it satisfies certain constraints that.
Chapter 6 1 © Prentice Hall, 2002 The Physical Design Stage of SDLC (figures 2.4, 2.5 revisited) Project Identification and Selection Project Initiation.
MS Access: Creating Relational Databases Instructor: Vicki Weidler Assistant: Joaquin Obieta.
Copyright 2008 McGraw-Hill Ryerson 1 TECHNOLOGY PLUG-IN T5 DESIGNING DATABASE APPLICATIONS.
Normalization Information Systems II Ioan Despi. Informal approach Building a database structure : A process of examining the data which is useful & necessary.
Chapter 10 Normalization Pearson Education © 2009.
ITN Table Normalization1 ITN 170 MySQL Database Programming Lecture 3 :Database Analysis and Design (III) Normalization.
Rules of Database Normalization
©NIIT Normalizing and Denormalizing Data Lesson 2B / Slide 1 of 18 Objectives In this section, you will learn to: Describe the Top-down and Bottom-up approach.
In this session, you will learn to: Describe data redundancy Describe the first, second, and third normal forms Describe the Boyce-Codd Normal Form Appreciate.
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,
Database Terms t DBMS –Database Management System. A software used to organise, analyse, store, retrieve, and edit information. –e.g., Visual FoxPro, Access.
Normalisation RELATIONAL DATABASES.  Last week we looked at elements of designing a database and the generation of an ERD  As part of the design and.
Flat Files Relational Databases
NORMALIZATION. What is Normalization  The process of effectively organizing data in a database  Two goals  To eliminate redundant data  Ensure data.
Understand Relational Database Management Systems Software Development Fundamentals LESSON 6.1.
NORMALIZATION: ‘1NF’ The general rule: ‘’Any field which can have many, must have its own table’’ By Sam Beaumont.
Normalisation 1NF to 3NF Ashima Wadhwa. In This Lecture Normalisation to 3NF Data redundancy Functional dependencies Normal forms First, Second, and Third.
Microsoft Access 2010 Chapter 11 Database Design.
Lecture 4: Logical Database Design and the Relational Model 1.
INFS 6220 Systems Analysis & Design Transactional DBs vs. Data Warehouses.
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.
MS Access. Most A2 projects use MS Access Has sufficient depth to support a significant project. Relational Databases. Fairly easy to develop a good user.
SQL Basics Review Reviewing what we’ve learned so far…….
Lecture # 17 Chapter # 10 Normalization Database Systems.
IT 5433 LM3 Relational Data Model. Learning Objectives: List the 5 properties of relations List the properties of a candidate key, primary key and foreign.
Normalisation FORM RULES 1NF 2NF 3NF. What is normalisation of data? The process of Normalisation organises your database to: Reduce or minimise redundant.
1 CS490 Database Management Systems. 2 CS490 Database Normalization.
NORMALISATION OF DATABASES. WHAT IS NORMALISATION? Normalisation is used because Databases need to avoid have redundant data, which makes it inefficient.
Flat file and relational databases Flat file database In a flat file database information is held in a single table. Student IDStudent name GenderDOBCourse.
Revised: 2 April 2004 Fred Swartz
Relational Model.
A brief summary of database normalization
Chapter 4 Relational Databases
Databases A brief introduction….
Entity relationship diagrams
Chapter 4.1 V3.0 Napier University Dr Gordon Russell
Relational Database Design
Databases 1.
BTEC ICT – Unit 18 With Mr Griffiths.
Presentation transcript:

CORE 2: Information systems and Databases NORMALISING DATABASES

 Normalising is the process of normalising the design of a database to exclude redundant data.  Redundant Data is unnecessary duplicate data. Reducing or preferably eliminating data redundancy is the aim of normalisation. When we normalise we re-design the database schema for a more logical organisation. It involves splitting the data into tables linked by relationships, aiming to reduce redundant data. Redundant data wastes storage space and creates maintenance problem. If duplicate data exists in different locations then changes must be made numerous times and if all copies are not altered then data integrity issues arise. Eg. A postal address changes for a supplier. NORMALISING DATABASES

 The normalisation process is theoretically performed by decomposing the design into a sequence of ‘normal forms’, where each normal form is a rule with which the database must comply.  Technically here are 8 forms that experienced database designers use to create ‘normal forms’. In IPT we will restrict our less-technical process down to 3 normal forms which we will call..  1NF – First Normal form  2NF – Second Normal form  3NF – Third Normal form NORMALISING DATABASES

 The first normal form deals with the removal of repeating attributes across horizontal rows and ensures each field holds only single data items. To achieve first normal form we must ensure… 1.Each field stores single data 2.There are no multiple data items within indv. fields and no fields are repeated.  Typically, to meet the above requirements, we perform the followings processes…  Splitting Fields into smaller units of data (to achieve 1)  Deleting repeated fields (to achieve 2)  Creating new records for each multiple data item and each repeated field (to achieve 2) FIRST NORMAL FORM (1NF)

 The second normal removes redundant data within vertical columns or fields. To achieve second normal form we must ensure… 1.All tables must be in first normal form. 2.Every non key attribute is functionally dependent on the table’s primary key.  Typically, to meet the above requirements, we perform the followings processes…  Determine Function Dependencies by looking at data redundancies records (horizontal) or fields (verticals).  Determine a primary key for each set of functionally dependent attributes.  Create new tables for each entity – populate new tables, delete data in old tables SECOND NORMAL FORM (2NF)

 The third normal removes further redundant data within vertical columns or fields. To achieve third normal form we must ensure… 1.All tables must be in second normal form. 2.Every non key attribute is functionally dependent on the table’s primary key and not on any other attributes of the table.  Typically, to meet the above requirements, we perform the followings processes…  Look for non-key attributes that are functionally dependent on another non-key attribute.  Determine a primary key for each set of functionally dependent attributes.  Create new tables for each entity – populate new tables, delete data in old tables THIRD NORMAL FORM (3NF)