MySQL AB __ An Introduction to Database Normalization - The Diigo Meta page

• 15 Dec 09
  

  Csaba Horvath

  "An Introduction to Database Normalization"

  database mysql design

• 21 Oct 09
  

  Kel Royal

  MySQL Intro to Database Normalization

  database mysql tutorial

• 15 Sep 09
  

  Javier Neira

  mysql database normalization tutorial codd

  • The first normal form (or 1NF) requires that the values in each column of a table are atomic. By atomic we mean that there are no sets of values within a column
  • One method for bringing a table into first normal form is to separate the entities contained in the table into separate tables
  • 12 more annotations...
  • • surrogate primary key -- an artificial primary key used when a natural primary key is either unavailable or impractical.
    • when using a surrogate primary key it is still important to create a UNIQUE key to ensure that duplicate records are not created inadvertently (but some would argue that if you need a UNIQUE key it would be better to stick to a composite primary key).

    • There are various types of relationships that can exist between two tables:

      
      
      
      • One to (Zero or) One
      • One to (Zero or) Many
      • Many to Many
    • To represent a many-to-many relationship in a relational database we need a third table to serve as a link between the two.
    • When we have a one-to-many relationship, we place a foreign key in the table representing the �many�, pointing to the primary key of the table representing the �one�.
    • Columns in a table that refer to primary keys from another table are known as foreign keys, and serve the purpose of defining data relationships.
    • the Second Normal Form (or 2NF) deals with relationships between composite key columns and non-key columns.
    • The second normal form (or 2NF) any non-key columns must depend on the entire primary key. In the case of a composite primary key, this means that a non-key column cannot depend on only part of the composite key.
    • To bring the Review table into compliance with 2NF, the Author_URL must be moved to the Author table.
    • Third Normal Form (3NF) requires that all columns depend directly on the primary key. Tables violate the Third Normal Form when one column depends on another column, which in turn depends on the primary key (a transitive dependency).
    • In the Publisher table the City and State fields are really dependent on the Zip column and not the Publisher_ID. To bring this table into compliance with Third Normal Form, we would need a table based on zip code:
    • With our tables now separated by entity, we join the tables together in our SELECT queries and other statements to retrieve and manipulate related data
• 29 Jun 09
  

  Joel Liu

  Mysql

• 27 May 09
  

  Muhammed Ettar

  JOIN Book

  design programming database data-process data-format data dataset sql Data-model normalization

• 31 Mar 09
  

  Carl at_EHU

  Work ICT reldatabases

• 20 Mar 08
  

  atin sood

  dbms mysql normalization tutorials

• 30 Nov 07
  

  ento entotto

  database del.icio.us design mysql normalization programming tutorial

• 19 Oct 07
  

  Nguyen Tien Si

  Over the years I, like many of you, have had the experience of taking over responsibility for an existing application and its associated schema (sometimes frustratingly woven together as part of a Microsoft Access solution).

  database normalization mysql tutorial databases sql design

• 07 Sep 07
  

  Navneet Kumar

  mysql normalization Database

• 07 Jul 07
  

  crankbos

  database databases db design development mysql normalization programming tutorial

• 27 Dec 06
  

  Jean-Marc Fontaine

  de normalisation mysql base donnée

• 02 Aug 06
  

  vivpuri

  mysql

• 24 Jul 06
  

  Dan Perry

  cs::databases mysql

• 06 Jun 06
  

  Sonja Tomaskovic

  database normalization Datenbank

• 05 May 06
  

  Francisca Munoz

  cs::databases

• 12 Jan 05
  

  c user

  code

  • When users ask for advice about their database applications, one of the first things I try to help them with is the normalization of their table structure. Normalization is the process of removing redundant data from your tables in order to improve storage efficiency, data integrity and scalability. This improvement is balanced against an increase in complexity and potential performance losses from the joining of the normalized tables at query-time.
• 29 Oct 04
  

  tadej zontar

  Database

Page Comments

• 
  vivpuri on 2006-08-02
  Database Normalization

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.