Minty's Avatar
Newbie Member
what do u do with tables having many to many relaionship.
because in the erd we make another table of containing the primary keys of both the tables.

its confussinnnn me how we change those tables in inf
vikas1234's Avatar, Join Date: Aug 2008
Go4Expert Member
nice short tutorial on normalization ... I just would like to add that that too much normalization make lots of table so you should always go for optimal normalization ...
pradeep's Avatar, Join Date: Apr 2005
Team Leader
Very right said Vikas!
satyedra pal's Avatar, Join Date: Mar 2010
Normalization is the process of organizing data into tables in such a way that the results of using the database are always unambiguous or
the process of organizing data to minimize redundancy. Normalization divides a database into two or more tables and links relationships between the tables
Normalization is done in two step that puts data into tabular form by removing redundent data and then removes duplicated data from the relational tables.
In normalization we do:
Avoiding repetitive entries.
Increased speed and flexibility of queries.
Reducing required space of storage for data by removing redundent data.

It has following normal form:
1NF(Normal form)
smithshn's Avatar
Light Poster
When data records are in large form then there is required normalization.
Normalization is a process of removing data which is repeated and filtering data to identify a value as uniquely in a table.
In RDBMS there is different method for normalization of the records which is shown as below:
(1) 1st Normal Form
(2) 2nd Normal Form
(3) 3rd Normal Form
(4) 4th Normal Form
(5) 5th Normal Form
(6) BCNF - Boyce Codd Normal Form- In this normal form you have follow the 32 rules of it.
seomanju's Avatar
Thanks for this detail.
seomanju's Avatar
Data models are the techniques to handle our databases.
sneha123's Avatar
Go4Expert Member
Originally Posted by pradeep View Post
Functional Dependency

Definition: A functional dependency occurs when one attribute in a relation uniquely determines another attribute. This can be written A -> B which would be the same as stating "B is functionally dependent upon A."
Examples: In a table listing employee characteristics including Social Security Number (SSN) and name, it can be said that name is functionally dependent upon SSN (or SSN -> name) because an employee's name can be uniquely determined from their SSN. However, the reverse statement (name -> SSN) is not true because more than one employee can have the same name but different SSNs.

Transitive Dependency

Definition: A type of functional dependency in which the value in a non-key field is determined by the value in another non-key field and that field is not a candidate key
Hello Pradeep,,,,sneha here,,its excellent job,,,,,Thanks lot for share with us,,,,,,,,,
samantha1230's Avatar
Thanks for letting me know about Normalization, I just heard this but now come to know what exactly it is.