Solved

database normalization

Posted on 2006-06-24
10
2,332 Views
Last Modified: 2008-01-09
I don't have a formal background in relational theory and I'm trying to get a better understanding of normalization.  I'm trying to find examples and more information on 1nf - 3nf, which seems to be appropriate for many smaller applications.  I want to get a good handle on these.

1NF - Eliminate Repeating Groups - Make a separate table for each set of related attributes, and give each table a primary key.

2NF - Eliminate Redundant Data - If an attribute depends on only part of a multi-valued key, remove it to a separate table.

3NF - Eliminate Columns Not Dependent On Key - If attributes do not contribute to a description of the key, remove them to a separate table.

Can anyone point me to some good resources.
0
Comment
Question by:-Dman100-
  • 2
  • 2
  • 2
  • +3
10 Comments
 
LVL 1

Assisted Solution

by:dwhite365
dwhite365 earned 100 total points
ID: 16976897
OReilly SQL In a Nutshell has a short section covering normalization requirements that takes care of the practical aspects of it.
0
 

Author Comment

by:-Dman100-
ID: 16976907
anything online?  Examples?
0
 
LVL 26

Expert Comment

by:DireOrbAnt
ID: 16976985
0
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 
LVL 26

Assisted Solution

by:DireOrbAnt
DireOrbAnt earned 100 total points
ID: 16977013
The wiki entry is quite nice, but you can scroll to the bottom and go to the "Further reading" and "External links" sections.

As for what you should apply to your project, the best answer I can give you is to try to understand all normal forms (there are more than 3), maybe excluding 6 ;) and to apply as much of them as possible. In a very small project, that won't get tons of hits/data and won't extend into a bigger apps, you can ignore most and get you projejct out though :)

Hope you find what you are looking for in there.
0
 
LVL 16

Expert Comment

by:MohanKNair
ID: 16977361
0
 
LVL 16

Assisted Solution

by:MohanKNair
MohanKNair earned 100 total points
ID: 16977365
0
 
LVL 9

Expert Comment

by:david_levine
ID: 16978512
Are you looking to find out how to do it, why to do it, how do it for some specific example you have?

Doing it just to do it is fine for a classroom and fine for many real life examples, but there are valuable reasons to not do it too, depending on what your application is, how often data is updated, etc.

Theory is just theory and real life sometimes trumps theory.
0
 

Author Comment

by:-Dman100-
ID: 16979311
Thanks for the information.

No, this isn't for a classroom.  I work as a web developer and have been using SQL Server now for about 3 years.  Typically, most of my development has been data extraction, updates, inserts, deletions, etc.  I haven't done too much with actual modeling and design.  Albeit, I have done some design.

I'm getting more involved in the actual design and trying to expand my knowledge base on normalization and relational theory to help me be more effective in my development.

So, how to do it and why to do it certainly applies in my case.  I'm not completely in the dark to fundamental normalization concepts.

Does that help explain?
0
 
LVL 9

Accepted Solution

by:
david_levine earned 100 total points
ID: 16979362
Based on your past experience using SQL, you're likely well prepared for determining the application impact your design will cause. What needs to be done for a transactional application could be the same or very different from a design for a data warehouse application.

How the data will be used initially and built on over time helps determine the optimal plan of attack in designing a database.

I'm sure you already know, if the folks designing the tables you've been using are doing a good job, that most data elements reside in only 1 table with the keys of the records referenced in other tables. Lookup tables are typical in many applications and the keys to those records are stored in the other tables.

If you're looking for online references, a Google search for: practical database design
seems to turn up a lot of relevant links.

If you're looking for printed material, an Amazon book search on the same keywords turns up a bunch of what looks like pretty on topic references to learn or refer to:
http://www.amazon.com/exec/obidos/search-handle-url/103-0483154-2688667?%5Fencoding=UTF8&search-type=ss&index=stripbooks%3Arelevance-above&field-keywords=database%20design
0
 
LVL 9

Assisted Solution

by:gabeso
gabeso earned 100 total points
ID: 16979841
C J Date is a good writer on issues regarding relational databases see his books for an in-depth understanding of the relational model - as opposed to a vendor specific implementation of it (which of course all vendors support to various degrees of over-kill!)

If you are interested in understanding it you should investigate the concept of 'functional dependency' - which is the concept which underlies all of the normal forms.

A functional dependency is essentially a functional relationship between one value and another:

f(x) = y. If one x determines one y then you have a functional dependency between them - if one x determines many y's then you have a multivalued dependency between them.

If you start to analyze your information into "this determines that" so that you can follow a logical chain between one value and another you will have your information in a normal form i.e. it will be correct.

Tables just become dependencies collected together appropriately according to requirements of storage perhaps or other factors in your design.

0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article describes some very basic things about SQL Server filegroups.
SQL Command Tool comes with APEX under SQL Workshop. It helps us to make changes on the database directly using a graphical user interface. This helps us writing any SQL/ PLSQL queries and execute it on the database and we can create any database ob…
Video by: Steve
Using examples as well as descriptions, step through each of the common simple join types, explaining differences in syntax, differences in expected outputs and showing how the queries run along with the actual outputs based upon a simple set of dem…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

823 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question