Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

James Serra's Blog

James is currently a Senior Business Intelligence Architect/Developer and has over 20 years of IT experience. James started his career as a software developer, then became a DBA 12 years ago, and for the last five years he has been working extensively with Business Intelligence using the SQL Server BI stack (SSAS, SSRS, and SSIS). James has been at times a permanent employee, consultant, contractor, and owner of his own business. All these experiences along with continuous learning has helped James to develop many successful data warehouse and BI projects. James has earned the MCITP Business Developer 2008, MCITP Database Administrator 2008, and MCITP Database Developer 2008, and has a Bachelor of Science degree in Computer Engineering. His blog is at .

Normalizing Your Database

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

Stairway to Database Design Level 9: Normalization

Third Normal Form

Comments

Leave a comment on the original post [www.jamesserra.com, opens in a new window]

Loading comments...