Discuss anything here - everything that you wish to discuss with fellow engineers.
Join this group to post and comment.
Can somebody help to get a clear concept of SQL Normalization .
Check out this video. It is very easy to understand and the concept is explained well using MS SQL Server... 😀
Yeah sure. Where are you stuck at? I mean what part you did not understand? I can help.AbhishekBiswasCan somebody help to get a clear concept of SQL Normalization .
infact could you guide me a lil , ,i gt a very lil knlege in this . Thanks in adv.AbraKaDabraYeah sure. Where are you stuck at? I mean what part you did not understand? I can help.
AbraKaDabraYeah sure. Where are you stuck at? I mean what part you did not understand? I can help.
Did you people see the video posted by me? 😛AbhishekBiswasinfact could you guide me a lil , ,i gt a very lil knlege in this . Thanks in adv.
SQL Normalization is a term not heard of. SQL is a language used for accessing Relational Databases, the language is non-procedural, statement like, that we use in real life. Normalization is a process in a database to create such tables (called relations) which only represent a set of particular type of entity in the database. The process entails gathering the attributes only relevant to the information for a particular type of entity. For example, if I want to maintain the data about students who are offered training in some discreet subjects in IT and create a table having columns - student id, subject, fees, phone num - then such table would not be appropriate as per principles of RDBMS, since such tables contain the data about the students and subjects as well (2 types of entities). So when we apply principles of normalization here, then the table would be first split into two - student id, phone, subject and another table subject, fees. Since in this fees is relevant to subject (so is subject information) and phone is relevant to student id (so is students' information). The splitting is based on a concept of dependency which has arithmetic base and for more info, if allowed on this site, may I redirect you to : https://crazy4db.blogspot.in/2012/03/database-design-normalization-normal_14.html
Hey, I also found this very simple and well explained article - https://azabani.com/blog/2012/05/understanding-database-normalisation/
I have gone through this article/blogpost. A great article indeed. But here I am reproducing a line from this post. "Database normalisation is the process of arranging the layout of a database's fields and tables with the aim of minimising dependency and redundancy."kidakakaHey, I also found this very simple and well explained article - https://azabani.com/blog/2012/05/understanding-database-normalisation/
The underlined and emboldened part "minimizing dependency" is quite not a heard of term. Technically there is no action such as "minimization" of dependency. There are three types of dependencies - Functional, Partial and Transitive. Of the three a relation is said to be well structured with the functional dependency, while other two types of dependencies, if present, then they give rise to insert, update, delete anomalies and data redundancy, hence undesirable. Of course partial dependency CAN only exists in cases if the relation has composite primary key. Transitive dependency is observed when a non-key has functional dependency on another non-key attribute. Decomposition (splitting) of the table with the aim to separate out those dependent columns along with their keys (columns on which they depend) is part of the process of normalization but I have some reservation about the use of emboldened term in the definition of Normalization.
Following ... thanks for all supports😀