.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
 
Sign In
Register
 
Win Surprise Gifts!!!
Congratulations!!!


Top 5 Contributors of the Month
david stephan

Home >> Forum >> Sql Server >> Post New QuestionBookmark and Share Subscribe to Forum

What is Normalization?

Posted By: Kshitish     Posted Date: August 06, 2008    Points:2   Category :Sql Server
Please help me understand normalization.

Kshitish

Responses
Author: Pankaj Mishra             
Posted Date: August 06, 2008     Points: 5   

Hi,
By definition Normalization is a technique for designing relational database tables to minimize duplication of information.

Cheers
Pankaj

Author: Savi3             
Posted Date: August 26, 2008     Points: 5   

It also can said like filtering the repeated datas

Author: Abhisek Panda             
Posted Date: December 13, 2009     Points: 5   

We use normalization to less the number of duplication in our table. It helps in reducing redundancy.

Author: Lalij Mer             
Posted Date: January 29, 2010     Points: 5   

The process of removing redundant data by creating relations between tables is known as Normalization. Normalization process uses formal methods to design the database in interrelated tables.


It is possible to start creating the database at this point. It's just a question of creating a new table for every entity identified in the diagram. We'll be using MS-Access to do that shortly. But how do you code the relationships?

There is a formal process to do that in database modeling. It's called normalization. It means applying a set of rules to the data so that you group the attributes in such a way that the relationships work. It's not really that complicated but it is a formula approach. If you prefer to use that approach, get any good book on databases, look-up "normalization" and follow the steps.

We'll do normalization using the intuitive approach - work with the data until it "feels" OK. This could also be called prototyping - create a working model of the database that is close to what you want and keep improving it until it works perfectly, then put it into production.

However, whatever the approach taken, there are some basic rules that have to be adhered to. The rules apply to any relational database and cannot be broken. They can't even be stretched. Think of them as the Prime directives. The rules are:

1. Every table must have a primary key - an attribute or combination of attributes that uniquely identifies every occurence in the table.

2. The primary key can never contain an empty or Null value. That makes sense - if you had 2 that were empty, they wouldn't be unique anymore.

3. Every attribute of every occurence in the table can contain only one value. Think of the Employee table as a grid. Every occurence, or line, represents one employee and every column is an attribute. So, every employee can only have one ID and one First-name and one Last-name, and so on.


Please Check my answer if you help....
Thank You...

Lalit.
Author: Dhivakaran             
Posted Date: November 23, 2010     Points: 5   

Normalization: is a process of organizing data and minimizing redundancy of database.

-
Dhivakaran T
Author: Narayanan             
Posted Date: July 20, 2011     Points: 20   
Author: BitWise             
Posted Date: August 24, 2012     Points: 20   

http://db.grussell.org/section008.html
Just Go through this....

BitWise


Post Reply

You must Sign In To post reply
 
 
Find more Forum Questions on C#, ASP.Net, Vb.Net, SQL Server and more Here
Quick Links For Forum Categories:
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  OOPs  SilverlightIISJQuery
JavaScript/VBScriptBiztalkWPFPatten/PracticesWCFOthers
www.DotNetSpark.comUnAnsweredAll

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend