Love these videos. Very helpful for explaining normalization. They're much easier to understand than most videos out there. It's also nice to see some humor thrown in.
I honestly admit after hours spent on searching for videos about database normalisation, that this is the clearest one that i found. Congrats and thanks again, you saved my day. I finally got a good understanding of the topic.
You are the GOD(Greatest of DBMS). No other youtube video could explain Normalization in a way that you did. Really feeling confident now. Thanks a ton! :-)
@@ComputerScienceLessons Thankyou :-) Could you Please post a Boyce Codd Normalization explanation too? I understood the 1NF, 2NF, 3NF, thanks to your video. But I am unable to understand BCNF(mainly the "multi-valued dependency" concept) Thanks for your help bro :D
You did a great job! Thanks for your work. I agree about how effective it was to use the same examples in the 3 videos. That helped to normalize the videos with the normal form number being the key 😅
Thanks a lot. It really helps me in understand those three normal form. Please make also for BCNF... I really had a hard time understanding this concept BCNF Thank you.
Thanks for the lovely comment. I should probably put more effort into publicising my channel - but it is growing organically. Please spread the word. :)KD
Soon we will be forced to put genders in a separate table as well, since people are starting to change them regularly as they change address :D. Thank you very much from Rome, it was a very beautiful tutorial!
i have a question, you said the grade is drived from exam mark, and it is violated 3NF, and we need to create a new table: result. but what primary ID should we set for result? right now, i am doing my project, i have a table: BillingInfo (billingID, bookID, number_of_book, price), the price is drived from bookID and number of book, so i guess i need to seperate this into two tables, but i don't have any idea how to decomposite a new table
I'm confused. In your 2NF video, you say "a table should only contain data about one type of thing" to be in 2NF. But in Courses (at 3:30) it clearly contains data about two different things - Courses and Teachers. So I don't understand how it is in 2NF? I'm lost on the difference between 2NF and 3NF.
Hi Dominic. In this specific example, each course has its very own teacher and there are no teachers here that teach more than one course, so, arguably, the information about each teacher is actually information about the course. If however, Mr Einstein taught Chemistry AND Physics, then the Courses table would not be in 2NF. You could also argue that since some of the courses have the same Fee, then the Fees should be in a different table to meet the criteria for 2NF. In the past I have seen problems in which the data were totally abstract (letters and numbers only, and column names like Col1, Col2, Col3, etc.). Theoretically, you can normalise such tables by following a set of rules. I must say however (at the risk of muddying the water for you), I see little real world value in abstract problems like this. It's more important to know your data and what you want to do with it; common sense and and instinct play an important role in database design (someone will probably object to that statement!). You are therefore correct to say that a teacher is a different thing and belongs in its own table. A final point, a fully normalised database is not always the best solution to a problem; take a look at NoSQL. :)KD
Great examples! But unless you previously defined key and primary key in some nonstandard way, I believe your definition is slightly inaccurate. AFAIU wherever you said "primary key" you should replace it by "any candidate key", and then by a "non key" attribute you presumably mean a non-prime attribute, that is an attribute that is not part of any candidate key... because every attribute is at least part of the whole scheme as a superkey.
I have a question (excuse me if this is too dumb😅): Isn't the Last Name also dependent on First Name? For instance, if someone else has to be assigned the same id as Kevin Drumm, wouldn't we need to change both the last name and the first name? Shouldn't this also be a violation of 3rd normal form?
there is already a partial dependancy as well. where course tittle, teacher id -> teacher name and teacher id -> teacher name. so it cannot pass through 2NF..correct me if i am wrong
Hi! I like your videos because its easy to understand. Im struggle to make a slides for my presentations and I'm also new in IT field huehue, but do you have a videos about the advantages of relational database?
Would fees not have its own table since there are duplicate fees, e.g. 1800 for Physics and 1800 for Chemistry. So a table called Fees, which has Fee ID (primary key) and fee (int) and hell... even Qualifcations could have its own table too. Actually, I think that might be 4NF...
7:32 "Every student has a gender, but it doesn't really make sense to put genders in a separate table." Had a nice little chuckle out of that one... with the way multi-gender culture is going...
Because, in this scenario, the course title is unique and can therefore serve as a primary key. In practice, a course ID might be included because it can save confusion when you have similar course titles, and it's easier to quote when people make bookings.
He is an example of a Great Teacher. They are hard to come by. There are other videos on this very same topic that are not explained as well as this person does it.
Hi Nadeesha. As long as a table includes a column with unique values, then this column can serve as the primary key. If the Course Title is always unique, this can be the primary key. If a COMBINATION of columns for any given record is always unique, then this combination can serve as a 'composite' primary key. What you choose for a primary key depends on the nature of the data. Having said that, I've worked with a number of organisations where database designers were encouraged to always include a surrogate primary key (a single column whose only purpose is to serve as a primary key). In this example, you would include a new CourseID column. This makes life easier for people programming the front end. :)KD
@@ComputerScienceLessons If the course title could change (e.g. from Mathematics to Maths) would that make it inelligable (or maybe just a poor choice of) primary key?