b_book1.gif (162 bytes)Data analysis | Database

Normalisation - relational data analysis

danorm1.gif (4717 bytes)

  • b_dfn.gif (837 bytes)Normalisation:
    • Structuring data to achieve data integrity.
    • The process of converting complex data structures into simple stable data structures.
    • It is an approach that examines data and groups data items in a way that seeks to minimise the impact of change by reducing the duplication of data, represents data in form of a two dimensional table (refer Relational Database)
  • Objectives:
    • Prevent insert/update and delete anomolies
    • Minimise redundancy (produces controlled redundancy)
  • An entity is normalised when it is
    " Dependent on"
    • the key                     = first normal form
    • the whole key          = second normal form
    • nothing but the key = third normal form

Once you have normalised your data you may have to go back and review your Entity Relationship diagrams

Notation

PartId SupplierId*

PartPrice

X-U1 1345 12.50
F-16 1345 100.75
MIG-24 3889 15.89
B-767 3889 349.98
B-52 9876 88.00
X-U1 9876 34.59
SupplierId SuppName SuppDetails
1345 R.U.Short 12 Urgent Av
3889 Robin Banks 12 Wall St
9876 Ray Zerr 18 The Cut
: : :
danorm2.gif (3831 bytes)
  • Entity = A related set of data eg. Supplier.
  • Data element = A unit of data forming an item or a field eg. SuppName
  • KEY unique identification key
    • Atomic key = key with single attribute
    • Compound key = key with mutiple attributes
    • Primary key = A unique identifier by which the data may be located eg. SupplierId.
    • Foreign key* = key of a related table
  • ATTRIBUTE
    • Mandatory = must have (not null).
    • Optional =  could have null or missing value
  • Projection is the elimination of columns on a table, removing duplicate rows
  • Join is the inverse of projection

Acknowledgement: S. Corich  EIT 1998, K. Allpress Unitec 99
[Rev 16/05/99] 13/6/97  © 1997-99 V/2-Com (Verhaart), P O Box 8415, Havelock North, New Zealand.