Getting Started with Adobe After Effects - Part 6: Motion Blur


Upload Image Close it
Select File

Career advice for the IT professional
Browse by Tags · View All
SQLServerPedia Syndication 194
SQL Server 60
SSAS 40
#SQL SERVER 19
SSIS 18
2012/Denali 17
Career 17
Denali 14
SQL Server 2012 13
MDS/MDM 12

Archive · View All
June 2011 20
August 2011 15
July 2011 15
March 2012 15
October 2011 14
September 2011 14
May 2011 13
November 2011 12
February 2012 11
April 2012 10

James Serra's Blog

Normalizing Your Database

Jan 6 2012 12:00AM by James Serra   

If you’ve been working with databases for any length of time, you have heard the term normalization.

Normalization is the process of efficiently organizing data in a database.  There are two goals of the normalization process: eliminating redundant data (for example, storing the same data in more than one table) and ensuring data dependencies make sense (only storing related data in a table).  Reaching these two goals reduces the space used by the database and ensures the data is stored logically.

Guidelines have been developed to confirm that databases are normalized.  These are referred to as normal forms and are numbered from one (the lowest form of normalization, referred to as first normal form or 1NF) through six (sixth normal form or 6NF).  However, the 5th and 6th normal forms are rarely used, so I’m not going to mention those below.  Also note that most database architects start out designing in 3rd normal form, so it’s not necessary to perform these normalizations in order.

First Normal Form (1NF)

First Normal Form (1NF) sets the very basic rules for an organized database:

  • Eliminate duplicative columns from the same table
  • Create separate tables for each set of related data
  • Identify each row with a unique column (the primary key)

Second Normal Form (2NF)

Second normal form (2NF) further addresses the concept of removing duplicative data:

  • 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

Third Normal Form (3NF)

Third normal form (3NF) goes one large step further:

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

Boyce-Codd Normal Form (BCNF or 3.5NF)

The Boyce-Codd Normal Form, also referred to as the “third and half (3.5) normal form”, adds one more requirement:

  • Meet all the requirements of the third normal form
  • Every determinant must be a unique primary key (candidate key)

Fourth Normal Form (4NF)

Finally, fourth normal form (4NF) has one additional requirement:

  • Meet all the requirements of the third normal form
  • A relation is in 4NF if it has no multi-valued dependencies

More info:

Database Normalization Basics

First, second, and third normal form

Database Normalization: First, Second, and Third Normal Forms

Description of the database normalization basics

Video Normalisation Demonstration

Republished with author's permission. See the original post here.


Republished from James Serra's Blog [70 clicks].  Read the original version here [32134 clicks].

James Serra
35 · 5% · 1664
2
 
0
Lifesaver
 
0
Refreshed
 
0
Learned
 
0
Incorrect



Submit

2  Comments  

  • Mnemonic for first three laws: "The key, the whole key, and nothing but the key, so help me Codd"

    commented on Jan 10 2012 9:49PM
    Paras Doshi
    16 · 10% · 3265
  • @Paras.... that's great!

    Normalization is great for transactional OLAP databases when supporting INSERT, UPDATE and DELETE operations. It means the minimum amount of information is necessary for each. An insert requires all required columns in a table to be supplied, and UPDATE and DELETES only require a key or criteria.

    Where normalization hurts is in SELECT or reporting scenarios because it forces the use of JOINs. This is why denormalization is often the first and best strategy for increasing performance. Denormalization has its own costs, as denormalized tables are expensive to INSERT, UPDATE and DELETE.

    Most systems will contain a mix of 3NF and denormalized data; each supporting the functional that make sense. Transactions will often be executed against normalized tables and reporting will be executed against denormalized tables, with a process to keep them synchronized. Think OLTP->ETL->ODS->ETL->Data Warehouse->Data Mart. As you move from left to right, you will see increasingly denormalized structures.

    commented on Jan 28 2012 7:57AM
    Marc Jellinek
    97 · 2% · 556

Your Comment


Sign Up or Login to post a comment.

"Normalizing Your Database" rated 5 out of 5 by 2 readers
Normalizing Your Database , 5.0 out of 5 based on 2 ratings
    Copyright © Rivera Informatic Private Ltd Contact us      Privacy Policy      Terms of use      Report Abuse      Advertising      [ZULU1097]