BTEC ICT – Unit 18 With Mr Griffiths.

Slides:



Advertisements
Similar presentations
Normalisation.
Advertisements

Normalization Lite Pepper. Golden Rule Every attribute must depend upon the key, --- > 1NF the whole key, --- > 2NF and nothing but the key. -  3NF and.
Normalisation Ensuring data integrity in database design 1.
Athabasca University Under Development for COMP 200 Gary Novokowsky
Database Design Conceptual –identify important entities and relationships –determine attribute domains and candidate keys –draw the E-R diagram Logical.
Understand Normalization
1 NORMALISATION. 2 Introduction Overview Objectives Intro. to Subject Why we normalise 1, 2 & 3 NF Normalisation Process Example Summary.
Project and Data Management Software
July 14, 2015ICS 424: recap1 Relational Database Design: Recap of ICS 324.
Database – Part 2a Dr. V.T. Raja Oregon State University.
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)
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 Chapter 1 Overview of Database Concepts. 2 Chapter Objectives Identify the purpose of a database management system (DBMS) Distinguish a field from a.
RELATIONSHIPS Generally there are two main database types: flat-file and relational.
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.
Normalization (Codd, 1972) Practical Information For Real World Database Design.
CORE 2: Information systems and Databases NORMALISING DATABASES.
MS Access: Creating Relational Databases Instructor: Vicki Weidler Assistant: Joaquin Obieta.
Chapter 1Introduction to Oracle9i: SQL1 Chapter 1 Overview of Database Concepts.
1 Database & DBMS The data that goes into transaction processing systems (TPS), also goes to a database to be stored and processed later by decision support.
Btec National - Advanced Databases 1 Advanced Databases Entity Relationship Diagrams.
Relational Theory and Design
Normalization Is the gradual and sequential process of efficiently organizing data in a database that follows the rules listed in the previous slide –
BSA206 Database Management Systems Lecture 2: Introduction to Oracle / Overview of Database Concepts.
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.
Connecting (relating) Data Tables to get Custom Records (Queries) Database Basics.
Postgresql East Philadelphia, PA Databases – A Historical Perspective.
Btec National - IT SYSTEMS ANALYSIS AND DESIGN 1 IT Systems Analysis and Design Entity Relationship Diagrams.
Chapter 1 Introduction to Database. Database Concept Field: a basic data element or attribute of an object Record: a set of fields Table: a set of records.
Howard Paul. Sequential Access Index Files and Data File Random Access.
IST 220 – Intro to DB Lecture 4 Database Design thru ER Modeling.
NORMALIZATION Handout - 4 DBMS. What is Normalization? The process of grouping data elements into tables in a way that simplifies retrieval, reduces data.
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.
Flat file and relational databases Flat file database In a flat file database information is held in a single table. Student IDStudent name GenderDOBCourse.
Understanding Data Storage
Database, tables and normal forms
Revised: 2 April 2004 Fred Swartz
Databases – Exam questions
Unary Many-to-Many Relationship
Databases Chapter 16.
Database Normalization
Chapter 5: Logical Database Design and the Relational Model
What is IT? Preparation work for the BTEC Level 3 National Extended Certificate in Information Technology.
CSCI-100 Introduction to Computing
Chapter 4 Relational Databases
Design a Relational Database Identify Database Purpose
© 2011 Pearson Education, Inc. Publishing as Prentice Hall
Order Database – ER Diagram
Poor Naming Standards.
Normalization Referential Integrity
Relational Database.
Entity relationship diagrams
1st, 2nd, and 3rd Normal Forms
Chapter 4.1 V3.0 Napier University Dr Gordon Russell
Relational Database Model
Unit 18 Database Design Extended Diploma in ICT Julie Hodsdon
Database Normalisation
Data Management Innovations 2017 High level overview of DB
Computer Science Projects Database Theory / Prototypes
Lesson Objectives Aims You should know about: 1.3.2:
Database Design and Development
Getting to First Base: Introduction to Database Concepts
1st, 2nd, and 3rd Normal Forms
Getting to First Base: Introduction to Database Concepts
Lesson Objectives Aims You should know about: 1.3.2:
Getting to First Base: Introduction to Database Concepts
Understand the purpose of normalisation in terms of reducing duplication of data  Understand the purpose of Primary and Secondary Keys in a Database  Learning.
Normalisation 1 Unit 3.1 Dr Gordon Russell, Napier University
Presentation transcript:

BTEC ICT – Unit 18 With Mr Griffiths

Lesson 43 – P2 notes – Normalise own DB All students will: Normalise their own database Most students will: Understand Normalisation Some students will: Begin Assignment 3

P21 Notes – part 3 Normalisation Last lesson you learned what normalisation was (https://goo.gl/QSslpp) Now you need to show the steps you take from: An un-normalized database 1NF 2NF 3NF Use the slides that follow to help you normalise your Radio Station database (we are pretending it is not built yet)

Un-normalized database Here you show all the fields you think you will need in the database, minus the primary keys Eg for a database to store album details:

1NF Now show the same fields in 1NF Remember the rules to apply for 1st Normal Form are: Remove duplicate fields Create a table for each entity and add primary keys

2NF Rules for 2nd Normal Form: Meet all the requirements of the first normal form. Remove subsets of data that apply to multiple rows of a table and place them in separate tables. Create relationships between these new tables and their predecessors through the use of foreign keys.

3NF Meet all the requirements of the second normal form. Remove columns that are not dependent upon the primary key.