Database Normalisation: Third Normal Form

Поділитися
Вставка
  • Опубліковано 16 січ 2025

КОМЕНТАРІ • 129

  • @breefuller3124
    @breefuller3124 5 років тому +156

    Thanks for using the same example in all three videos

  • @michaelbruno4909
    @michaelbruno4909 5 років тому +39

    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.

  • @paoloberg70
    @paoloberg70 4 роки тому +9

    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.

  • @TidusfromZanarkand
    @TidusfromZanarkand 4 роки тому +5

    Quality examples, simple and clear explanations in all 3 videos about Normalization. Thank you, great work friend!!

  • @sanketkoli8641
    @sanketkoli8641 3 роки тому +2

    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
      @ComputerScienceLessons  3 роки тому

      You are very kind. :)KD

    • @sanketkoli8641
      @sanketkoli8641 3 роки тому

      @@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

  • @jeffreytello589
    @jeffreytello589 5 років тому +10

    best explanation of normalization on the internet! thank you

  • @1989Bismillah
    @1989Bismillah 5 років тому +9

    Simple and straight forward, thank you!

  • @georgefirth5631
    @georgefirth5631 4 роки тому +2

    This is an excellent deconstruction and has really cleared things up, thank you!

  • @philipmarno8730
    @philipmarno8730 2 роки тому +1

    Thank you for explaining this in such a consistent approach. Great set of videos.

  • @jeneydani
    @jeneydani 2 роки тому

    with this the second normal form became also clearer, most understandable videos that i found, thank you

  • @theletterpurple6228
    @theletterpurple6228 4 роки тому

    this nf series of videos is my go to when i need help with db schema. its explained so clearly

  • @jray1429
    @jray1429 2 роки тому +3

    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 😅

  • @srividia1
    @srividia1 2 роки тому

    Excellent explanation without unnecessary jargon. Thank you.

  • @emsdy6741
    @emsdy6741 5 років тому +8

    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.

  • @withyuva
    @withyuva 4 роки тому +1

    Best video on the topic, period. I wonder why other videos have more views than this one.

    • @ComputerScienceLessons
      @ComputerScienceLessons  4 роки тому +2

      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

    • @wijn_za
      @wijn_za 3 роки тому

      @@ComputerScienceLessons Hear, hear. Thank you for this!

  • @ezeakorosalyn1186
    @ezeakorosalyn1186 5 років тому +3

    God bless you immensely for this... You're really a good teacher

  • @monalimhetre4089
    @monalimhetre4089 3 роки тому +2

    thank you for explaining in detail with examples and in simple words.

  • @aventador1049
    @aventador1049 2 роки тому

    Best Normaization video in the universe for night before exam.

  • @Urquell-ty4eg
    @Urquell-ty4eg 5 років тому +1

    Great video series, thank you very much!

  • @hongkyulee9724
    @hongkyulee9724 2 роки тому

    Really thank you. Your videos are always so amazing.

  • @TheLord_M
    @TheLord_M 4 роки тому

    This is an amazingly simple explanation. Thank you

  • @realskater54211
    @realskater54211 2 роки тому +1

    U da man. Thanks for the informative video 💪🏽

  • @hugoirwanto9905
    @hugoirwanto9905 3 роки тому +1

    Crystal clear!

  • @rufina305
    @rufina305 3 роки тому

    Thank you so very much. I was searching for one examplé tha fits 1,2,3 normal forms and luckily I found yours. Thanks much again

  • @nakonachev1407
    @nakonachev1407 2 роки тому

    Greatly explained, thank you!

  • @nataliats114
    @nataliats114 5 років тому +1

    Thank you for the easy to understand videos

  • @dominicmorris819
    @dominicmorris819 3 роки тому +1

    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.

    • @ComputerScienceLessons
      @ComputerScienceLessons  3 роки тому

      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

  • @Wes-Tyler
    @Wes-Tyler 4 роки тому +1

    You have the best voice.

  • @latenews2024
    @latenews2024 3 роки тому +1

    Great
    work

  • @saumyasingh7216
    @saumyasingh7216 2 роки тому +1

    Awesome video

  • @saidshikhizada332
    @saidshikhizada332 3 роки тому +1

    great video! thanks.

  • @franzbiberkopf9179
    @franzbiberkopf9179 4 роки тому +1

    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!

  • @chrisalbers1370
    @chrisalbers1370 3 роки тому +1

    Life saver thank you!

  • @ranindugeekiyanage527
    @ranindugeekiyanage527 2 роки тому

    Best Explanation. thanx bro❤

  • @agcagigas4443
    @agcagigas4443 4 роки тому

    I can't find a video from your channel about BCNF. Are you able to create one, please?

  • @dumdumbringgumgum2940
    @dumdumbringgumgum2940 2 роки тому

    Thanks a lot 👏👏👏

  • @AC-fi8ge
    @AC-fi8ge 2 роки тому

    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...

  • @xixi3302
    @xixi3302 4 роки тому +1

    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

  • @RC_mentoring
    @RC_mentoring 5 років тому +4

    so many ahh ha moments wish i found this before all the other videos that ive been scraping through.

    • @manilakid3
      @manilakid3 3 роки тому

      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.

  • @shehrozmalik5961
    @shehrozmalik5961 4 роки тому

    Best Explanation

  • @TheLordQuick
    @TheLordQuick 3 роки тому +2

    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.

    • @ComputerScienceLessons
      @ComputerScienceLessons  3 роки тому

      I see where you're coming from. However, I often find that colloquial language better aids understanding. Nuance comes later. :)KD

  • @Cryptofins
    @Cryptofins 3 роки тому +1

    Why do we not need a course ID in this case?

    • @ComputerScienceLessons
      @ComputerScienceLessons  3 роки тому

      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.

  • @BruceWayne-yj7bd
    @BruceWayne-yj7bd 2 роки тому +1

    Wouldn't the last name dependent on the marital status, if its a female, therefore not be in 3rd normal form?

    • @ComputerScienceLessons
      @ComputerScienceLessons  2 роки тому +1

      Debatably! I'm sure there are plenty of females who did not change their last name when they got married who would argue against that. :)KD

  • @syaachan3533
    @syaachan3533 4 роки тому +1

    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?

  • @shaneschwalger2482
    @shaneschwalger2482 3 роки тому +1

    Thank you.

  • @Anteater23
    @Anteater23 Рік тому

    Do attributes that are foreign keys have to follow the same rules?

    • @ComputerScienceLessons
      @ComputerScienceLessons  Рік тому

      Attributes that are foreign keys are not particularly special. Any attribute can be a foreign key.

    • @Anteater23
      @Anteater23 Рік тому

      @@ComputerScienceLessons So a foreign key can be normalised out of a table?

  • @nadeeshaaravinda1372
    @nadeeshaaravinda1372 4 роки тому +1

    I wonder why the courses table doesn't have any ID.

    • @ComputerScienceLessons
      @ComputerScienceLessons  4 роки тому +4

      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

    • @JonHogg
      @JonHogg 3 роки тому

      @@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?

  • @vimukthaariyasinghe8041
    @vimukthaariyasinghe8041 3 роки тому

    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

  • @rustyspottedcat8885
    @rustyspottedcat8885 Рік тому +1

    Maximizing information content (sentences) from given amount of data (words) derived by relational logic.

  • @jackc87
    @jackc87 3 роки тому

    I want to take these courses with these professors.

  • @shreenthasleem2820
    @shreenthasleem2820 11 місяців тому +1

    Thank you sir

  • @snipo39
    @snipo39 Рік тому

    would you please make a video on BCNF

  • @siddharthsasikumar4271
    @siddharthsasikumar4271 4 роки тому +1

    Felt like watching a david Attenborough documentary.😍

  • @dhelmarxdancel2401
    @dhelmarxdancel2401 3 роки тому +1

    Can i use noodles for making database?

  • @akeemovic
    @akeemovic 3 роки тому

    Thanks very much.

  • @selinklnc4903
    @selinklnc4903 Рік тому +1

    love it

  • @HUGODTHERO
    @HUGODTHERO 4 роки тому +1

    the best

  • @riccoc.6507
    @riccoc.6507 2 роки тому

    OK thank you Bro makes sense

  • @meow-pk5gq
    @meow-pk5gq 2 роки тому

    Thank you

  • @anubhabbiswas4901
    @anubhabbiswas4901 3 роки тому

    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?

  • @bigopzooka
    @bigopzooka 9 місяців тому +1

    Wouldn't the Last Name have a transient dependency on the marital status? When someone marries they might take another last name ;)

  • @newjade6075
    @newjade6075 3 роки тому

    Thanks sir

  • @jeevanjohal8194
    @jeevanjohal8194 2 роки тому +2

    imagine being married while doing A levels lol

  • @meshuganah1
    @meshuganah1 4 роки тому

    2:26 "transient" should actually be "transitive" (I believe!)

    • @ComputerScienceLessons
      @ComputerScienceLessons  4 роки тому

      You are quite correct - oops! (I will upload a fix)

    • @meshuganah1
      @meshuganah1 4 роки тому

      @@ComputerScienceLessons thanks for the excellent video! I found it super helpful :)

  • @erickabogo1818
    @erickabogo1818 3 роки тому +1

    7:42 all 'The Simpsons' fans will see it

  • @ryank170
    @ryank170 4 роки тому +1

    Bro where do you go to school where a 70 is still a B?

  • @sterlingveil
    @sterlingveil 4 роки тому

    That last example fails if the exam is graded on a curve. In that case, the letter grade is free to change independently of the exam mark.

  • @moxie1855
    @moxie1855 5 років тому +1

    I saw a sherlock reference there

  • @throwaway-lo4zw
    @throwaway-lo4zw 10 місяців тому

    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...

  • @youssefnov9037
    @youssefnov9037 4 роки тому

    Can you help me teacher???

  • @martonburanszki9537
    @martonburanszki9537 3 роки тому

    You are wrong, the data must be in least the first normal form, it doesn't have to be in the second.

    • @ComputerScienceLessons
      @ComputerScienceLessons  3 роки тому

      It depends on what you are trying to achieve. Indeed, you may not want your data normalised at all. :)KD

  • @michaelerwin8744
    @michaelerwin8744 Рік тому

    In todays world I think it's inevitable to separate gender table on its own.

  • @supercoolaks
    @supercoolaks 8 місяців тому

    Poor example, it should not take 8 mins to state the 3NF and give a clear example smh

  • @NilakshMalpotra
    @NilakshMalpotra 3 роки тому +1

    :D

  • @chungus511
    @chungus511 5 років тому

    Database is such a fcking boring ****, but loved the video