Revised: 2 April 2004 Fred Swartz

Slides:



Advertisements
Similar presentations
Relational Terminology. Normalization A method where data items are grouped together to better accommodate business changes Provides a method for representing.
Advertisements

Chapter Three Objectives Identification of Keys Application of primary and foreign keys Converting a database design to Relational DB. What is a good DBMS.
Database Modeling IT Key Ideas, Dynamic Database Systems, 2002 Chapter 8.
Normalisation Ensuring data integrity in database design 1.
Database Design Conceptual –identify important entities and relationships –determine attribute domains and candidate keys –draw the E-R diagram Logical.
Microsoft Access 2002 By Ian Cole Lecturer in ICT.
Project and Data Management Software
Module Title? DBMS E-R Model to Relational Model.
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
Component 4: Introduction to Information and Computer Science Unit 6: Databases and SQL Lecture 4 This material was developed by Oregon Health & Science.
Normalization A technique that organizes data attributes (or fields) such that they are grouped to form stable, flexible and adaptive entities.
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.
Database Normalization Lynne Weldon July 17, 2000.
CORE 2: Information systems and Databases NORMALISING DATABASES.
MS Access: Creating Relational Databases Instructor: Vicki Weidler Assistant: Joaquin Obieta.
What's a Database A Database Primer Let’s discuss databases n Why they are hard n Why we need them.
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.
Database Design. The process of developing database structures from user requirements for data a structured methodology Structured Methodology - a number.
Component 4/Unit 6d Topic IV: Design a simple relational database using data modeling and normalization Description and Information Gathering Data Model.
Database Management Supplement 1. 2 I. The Hierarchy of Data Database File (Entity, Table) Record (info for a specific entity, Row) Field (Attribute,
Creating Databases Data normalization. Integrity and Robustness. Work session. Homework: Prepare short presentation on enhancement projects. Continue working.
Lection №4 Development of the Relational Databases.
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.
Howard Paul. Sequential Access Index Files and Data File Random Access.
IST 220 – Intro to DB Lecture 4 Database Design thru ER Modeling.
Microsoft Access 2010 Chapter 11 Database Design.
SLIDE 1IS 257 – Fall 2006 Normalization Normalization theory is based on the observation that relations with certain properties are more effective.
What Is Normalization  In relational database design, the process of organizing data to minimize redundancy  Usually involves dividing a database into.
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.
Logical Design & the Relational Model
Understanding Data Storage
Database Design.
Implementing an REA Model in a Relational Database
INLS 623 – Database Normalization
A Guide to SQL, Eighth Edition
Database, tables and normal forms
Relational Model.
Databases Chapter 16.
Normalization Karolina muszyńska
Database Normalization
Chapter 5: Logical Database Design and the Relational Model
CTFS Asia Region Workshop 2014
Chapter 9 Designing Databases
Relational Model and ER Model: in a Nutshell
© 2011 Pearson Education, Inc. Publishing as Prentice Hall
Normalization Referential Integrity
Relational Database.
The 1:M Relationship (continued)
Database Fundamentals
Database Normalization
Normalization By Jason Park Fall 2005 CS157A.
1st, 2nd, and 3rd Normal Forms
Database solutions The process of normalization Marzena Nowakowska Faculty of Management and Computer Modelling Kielce University of Technology rooms:
Relational Database Model
IST 318 Database Administration
Normalization.
Database Design Agenda
Normalization Normalization theory is based on the observation that relations with certain properties are more effective in inserting, updating and deleting.
1st, 2nd, and 3rd Normal Forms
Copyright © 2018, 2015, 20 Pearson Education, Inc. All Rights Reserved Database Concepts Eighth Edition Chapter # 2 The Relational Model.
INSTRUCTOR: MRS T.G. ZHOU
Normalization By Jason Park Fall 2005 CS157A.
Shelly Cashman: Microsoft Access 2016
BTEC ICT – Unit 18 With Mr Griffiths.
Presentation transcript:

Revised: 2 April 2004 Fred Swartz Database - Design Revised: 2 April 2004 Fred Swartz

DB - Tables = Entities = Nouns Problem "nouns" are represented as tables. Each row in a distinct instance. row = record = instance Each column is an attribute. column = attribute = property = field There are relationships between tables. Relationships are implemented with foreign-primary keys.

DB - Relationships 1:N One-to-many relationships. This is the standard type of relationship implemented with a foreign key on the many side pointing to a primary key on the one side. M:N Many-to-many relationship. These are common, but must be implemented in a relational database with a "bridging" or connection table that contains pairs of keys. 1:1 One-to-one relationship Not common, but used in superset/subsets.

DB - Entity-Relationship Approach Represent each entity as a table. Each row is one entity instance. Represent each attribute as a column. Repeating attributes must be in sep. table. Each row must have a primary key. Relationships implemented with keys. Multiplicity determined by business rules. M:N relationships need bridging table. Normalize to at least 3rd Normal Form.

DB - Normalization Normalization "forms" are guidelines to building effective relational databases. Normalizing often requires creating new tables and foreign keys. Areas normalization addresses Repeating values (make separate table) Computed fields (compute dynamically) Correct key and attribute identification. Eliminate redundant data Each level includes all previous levels.

DB - First Normal Form Each value must be "atomic". Different values should be separated. Eg, City and state. No repeating values in an attribute. Don't store a list of values in a column Don't use multiple columns for repeating values. Put repeating values in separate table with a foreign key to identify what they belong to.

DB - Second Normal Form Only applies to tables with composite primary keys (more than one column). Every non-key attribute must depend on the entire primary key. It can not be a fact about only some of the primary key columns.

DB - Third Normal Form Each non-key column must be a fact about the key column(s). "The key, the whole key, and nothing but the key".

DB - More Normal Forms Fourth Normal Form Fifth Normal From See pets and cars example. Fifth Normal From Boyce-Codd Normal Form