Video

great

The PK in the subscription table has repeating entries. How is that?

In Subscription table : there are 2 records with the same ID wilson44. The video stated that CustID is the PK, so this ID must be unique. I am confused.

Concise! Thanks

Yep. Great explanation. You uncomplicate what has been previously presented in a disjointed, convoluted manner. Thx ! What I needed, for sure.

Thank you so much. After 8 years it is still helpful

one of the best explanations on database normalization.

Thank you so much. Its first video out of 15 when I understand it

Your example for a 1st Normal Form table doesn't meet the requirement of rows being uniquely identified. Alan Smith could buy two Xbox Ones and ship them both to his address in Miami and there would then be two duplicate records. Needs an order id/qty column.

I have a question..? How can a Primary key column have repeating values? Is that possible? Like in the customer Table - Cust_ID = wilson44

Question: For 2NF, couldn't you make cust ID and Item a composite key that would determine all values in one table?

Key correction at 18:40 👉 In the Subscription Table and Sales Invoice Table: Cust ID should be the foreign key not the primary key. The reason being is that values in a primary key column must not, and indeed cannot, be duplicated. wilson44 is duplicated in both tables. To fix this the Subscription Table and the Sales Invoice Table must declare a distinct column as the primary key. 👉 Giving each subscription and sale invoice a unique number will make every entry distinct.

Thank you so much, you saved my time searching for this topic and not been able to find a video with this much details. You also explained it better than my lecturer Which clear my concept about table normalization till 4 normal form. I request you to please make a video on 3.5 n.f as well . ❤ You earn a subscriber here 👍

Hands down the greatest normalization example and explanation I have ever watched. He used one example straight through unlike others who like to switch the example once they reach 2nf and he explain partial dependency in layman terms than just textbook.

bolji od papica

I thought 2nd normal form should be not partially dependent (composite key). It looks like you did 3rd normal form in your 2nd normal form since it is a transitive dependency. Or am I wrong?

pffffffffff And shipping Address??!!! Should not break it in Address and City??????!!!!! Atomic value??????????!!!!

nice

I want a xbox for 250 please. ill take everyone the you have

Damn, you just made normalization easier. I was having trouble identifying dependencies but the way you explained it was as accurate and practical as hell. Thank you for this wonderful video!

1 add unique id, PK 2 check if all non key columns can be defined by PK, separate to 2 tables 3 no duplicated record, separate to entities 4 no multi value dependencies, non key columns relying on PK with duplicated records that are unable to be solved using new unique id. So, create new tables with PK+non key columns

Thanks for the video, what are the disadvantages if we include Newsletter in Item table?

Why did you remove and add different values that's not exist in the old tables? Its confusing and also the primary key is unique and not null. Bro? enlighten me

I’ve come to the conclusion that I’m just stupid, because this still makes no sense. Thanks for trying though🙏🏾

Clearly explained throughout the entire CZcams platform!

Thanks for this video!

One doubt How Cust ID could be a primary key, as the attribute value wilson44 is repetative

For the first time I've seen someone explain this clearly than my lecturers at school.

7 years later & this is still gold!

If you think my correction are correct, Sir. Please inform your viewer to watch here: czcams.com/video/KK_5lzqIuW0/video.html Thank you and God bless you, Sir.😁

Even though this video is 10 years old by now. It's the BEST explaination of a simple but effective implementation of objects that just works!!!

Really good video

Thanks for creating this video. Simple, crisp and to the point with proper example. Amazing video.

I cudnt understand this in my whole academic period

Too simplified. Many thanks.

I wonder would it be worthwhile to add a `NewsLetters` table and then a junction Table like `Customers_to_Newsletters` so that you are not storing newsletters multiple times? I guess an example would be if say the newsletter changed their name or something?

Great video was very helpful. However, in 4NF, the relation with Cust ID and Newsletter, shouldn't the Cust_ID be a foreign key not a primary key? It can't be a primary key because wilson44 shows up in multiple rows.

Such a great lecture. Thank you so much!

hm, can i just make new table for each column where i assign each (unique) line ID and then make table where i connect only those IDs to make starting table ?

wow, i didnt understand about repeating primary key in subscription table and sales invoice table, please someone help me,

Please, how many primary keys can you have/select/create in a 1NF?

Thank you very much for the explanation, the instruction is very clear and useful!

Best video ever

Thank you

You explained in 19 minutes what my professor tried to in 2 hours

czcams.com/video/xhY1lvANAvY/video.html

"Beautiful is not a color, it's an opinion" idk why that was funny to me.

thanks a lot, sometimes it helps to hear different people explain the same topic. and i listened to my prof but this time i had no idea what he meant. but now i know :D

Thanks bro

Love this tutorial. It's very precise, doesn't waste time, and gets to the point right away.