Your Department table won't work as you'll end up with repeating groups as you have EmployeeID in it. If you have a "Customer" Department for example and two employees then the "Customer" department would be repeated. You need an EmployeeDepartment table so a department can have multiple employees.
Thanks for the video. I would also like to ask a question. Is there a text or standard for normalization forms? I've noticed, after viewing multiple references to relational database design and normalization, that almost every person who writes and article, makes a video or lectures, almost always have a different definition of 1NF, 2NF, 3NF.... I know this is technology and software but is there an actual strict standard.
You missed that (FirstName, LastName) -> Initials The Initials depend on other attributes (the name) that are not primary keys hence 3NF is not yet satisfied !!
"Optimization" is really amiguous here !! You can optimize for less redundancy -> normalize You can optimize for speed and performance -> _denormalize_ Normalization is not necessarily "better"
Thank you for this video. I wish I would've found it 6 hours ago. :/
Out of curiosity. What software or website are you using to build your model?
thank you for this video. it's clear my all doubt.
1:14 1st Normal Form
2:24 2nd Normal Form
3:19 3rd Normal Form
For the future me. Maybe.
Your Department table won't work as you'll end up with repeating groups as you have EmployeeID in it. If you have a "Customer" Department for example and two employees then the "Customer" department would be repeated. You need an EmployeeDepartment table so a department can have multiple employees.
Brilliant stuff, thank you.
Well done . Thank you!
this is a really good video
it was really helpful
thanks a lot
thank you very much! this was quite easy to comprehend, even for an ol' fool like me, hehe :)) cheers!
I can't find any videos where there's a Employee and Customer primary key.. that's what we need !! 💔
Thanks 💯
Thanks for the video. I would also like to ask a question. Is there a text or standard for normalization forms? I've noticed, after viewing multiple references to relational database design and normalization, that almost every person who writes and article, makes a video or lectures, almost always have a different definition of 1NF, 2NF, 3NF.... I know this is technology and software but is there an actual strict standard.
It is more a definition of the normal forms. A good reference is: ISBN-13: 978-0133970777
@@srenspangsbergjrgensen2419 Thanks a lot.
You missed that
(FirstName, LastName) -> Initials
The Initials depend on other attributes (the name) that are not primary keys hence 3NF is not yet satisfied !!
What program is that?
Thanks man
Isn’t initials dependent on first name and last name for 3NF
Are you using Lucidchart?
Draw.io 😀
i need the pdf please
But I needed to see how you perform the 3NF! not just saying which will be which..
Which software you are using
Draw.io
"Optimization" is really amiguous here !!
You can optimize for less redundancy -> normalize
You can optimize for speed and performance -> _denormalize_
Normalization is not necessarily "better"
ممكن تفعيل الترجمة للفيديو