DBMS - Second Normal Form (2NF) Watch more Videos at www.tutorialspoint.com/videot... Lecture By: Mr. Arnab Chakraborty, Tutorials Point India Private Limited
I have used your videos several times sir, I have not written a "thanks" on each of them but here I'm going to thank you once for all of them. I appreciate it.
in course relation, there is a repetition of IS11 record, it will cause updation anomaly. IS11 should be IT11 in the second record else there will be no relation between student and course relation.
Sir, after splitting the table, you said there is no update anomaly. But if we see the Course relation, and if we want to update the title of Course ID - IS11, there can be update anomaly and that will restrict it from being in 2NF. Correct me if I'm wrong.
At 8:07 you have said that, 'Always remember if the relation does not have COMPOSITE KEY then it is in 2NF. But here in junction table [dbo.Registration] I've a composite key. ([CID, SID]) How?
What he said is If their is Only one Prime Attribute that means no Composite key, the relation will have Complete Functional Dependency. That is what we actually want in 2nf
you are right , Grade depends on SID and not on CID (Partially dependent )..... CID is not required when we are converting it to 2NF ....... Note : - a relation having composite key can be in 2NF if all the not key attributes fully dependent on all the attributes which contributes in composite key..
To Get Certification, Click Here: bitly.ws/PXXy
Use coupon "CZcams12" to get ‘’FLAT 12%’’ OFF at Checkout.
I have used your videos several times sir, I have not written a "thanks" on each of them but here I'm going to thank you once for all of them. I appreciate it.
Very well understood Thank u my proffessor of youtube
Thank you sir. Your vedio is best for the normalization.
thanks alot..always proud of tutorialpoint
It was very helpful .Thank you sir
Thank you sir for making this clear 😊
really good ra thooma sir
big fan saaar
Thanku sirr
in course relation, there is a repetition of IS11 record, it will cause updation anomaly. IS11 should be IT11 in the second record else there will be no relation between student and course relation.
Sir, after splitting the table, you said there is no update anomaly. But if we see the Course relation, and if we want to update the title of Course ID - IS11, there can be update anomaly and that will restrict it from being in 2NF.
Correct me if I'm wrong.
In course relation cid is primary key it should not contain duplicate value s
Best lecture
amazing!!!!
In course relation, CID IS11 has come for twice.
You are correct. We should omit one of them.
we need to keep common column in table
well explained
There is a little suggestion for you to please change the size of the text
At 8:07 you have said that, 'Always remember if the relation does not have COMPOSITE KEY then it is in 2NF. But here in junction table [dbo.Registration] I've a composite key. ([CID, SID]) How?
What he said is If their is Only one Prime Attribute that means no Composite key, the relation will have Complete Functional Dependency. That is what we actually want in 2nf
you are right , Grade depends on SID and not on CID (Partially dependent )..... CID is not required when we are converting it to 2NF ....... Note : - a relation having composite key can be in 2NF if all the not key attributes fully dependent on all the attributes which contributes in composite key..
can i get this material ? i need this script please
sir it's 'ANIL' not 'ONIL' but very nice explanation AND Thank you! for that!
Bengali's have this type of accent, try to learn but not to judge.
is se acha book hi parh leta yaar....
explain partial dependency in detail this explanation is not understandable
hina mir naam mera
you can teach it in hindi
WHAT THA FAK
Improve your English sir . Ur accent is hard
Improve your DBMS sir . Ur MARKS are hard😂😂😂😂