TABLE OF CONTENTS 00:00 - Intro 01:07 - 1st Normal Form 4:18 - 2nd Normal Form 9:44 - 3rd Normal Form 13:50 - 4th Normal Form 17:33 - Normalizing Customer Orders 20:35 - Customer Table (2NF) 21:55 - Product Table (2NF) 24:20 - Order Header vs Order Lines 29:05 - Product Table (3NF) 31:25 - Customer Table (1NF, 4NF)
@Kipviss3 жыл бұрын
nee.
@hooo2542 жыл бұрын
@@Kipviss .
@deepashankar083 жыл бұрын
That's brilliant, confused by a textbook but fully normalised now!
@organiz-izedtravis64116 жыл бұрын
This video will top the search results in youtube on "DB Normalization" going forward.
@4FrogsStacked2 жыл бұрын
Great explanation! It's obvious that you actually understand the topic well, and you're not just spewing out definitions. I've had some difficulty understanding these concepts until now
@girls_game_as_well43972 жыл бұрын
I have been struggling with this concept all week in class. I finally get it. Thank you so much.
@MaxProskoff3 жыл бұрын
Thank you for explaining this so clearly. I like the focus and the delivery.
@hectord.71075 жыл бұрын
I'm a total noob on this topic and watched many videos about database normalization, this is the simplest explanation on the topic and the one that helped me the most improving my database structure. Thanks a lot!
@montrealbudd28312 жыл бұрын
I really like this video. It was so much easier for me to understand normal forms by watching this video instead of reading my book. Thank you so much!
@harjos78 Жыл бұрын
Best explaination i have seen so far in any book or video!. Hats off. Great example and walk thourgh
@alexandercato74005 жыл бұрын
You did a great job teaching a complex topic in an understandable way! Just subscribed to your channel and expect you to get many more in the coming months because you’re producing quality content-it really stands out from the other videos on normalization. Keep up the great work!
@samiramir91samor782 жыл бұрын
Thank you so much, you just make it easy for me to understand, that what a perfect teacher looks like.
@chaslutterloh13095 жыл бұрын
Thank you! This was an excellent format for a visual learner like me!
@richod96353 жыл бұрын
Very well explained. This video tied up a loose ends for me. I already knew how to break apart one table into other tables, but this explanation really helped me to 100% confdent. Wouldn't it be a good idea to put 'Product Manufacturer Address' into it's own table in case the product is manufactured in multiple locations? If so, then what would be the key to the 'Product Manufacturer Address' table?
@vladyslavvlasenko43723 жыл бұрын
Thanks a lot! Your explanation is absolutely easy to understand, examples are perfect.
@skv4611 Жыл бұрын
Good explanation. After seeing the video, I felt like using pivot tables in Excel could speed up the process.
@fealgu100 Жыл бұрын
Simply great!
@KC-zn4gt5 жыл бұрын
Excellent video and clear explanation. Can't get better than this!
@raytierney63425 жыл бұрын
The absolute best !!!! Saving me from the land of total confusion!!!
@wanroslinawanmusa75323 жыл бұрын
Thanks. Very easy to digest explanation on normalization.
@kaedien4 жыл бұрын
At 8:25, when normalizing to 2NF, Mark Smith has a Titleist basketball and Bob Smith has a Spaulding basketball. A few seconds later after deleting rows from the Product table, Mark Smith has a Spaulding (note: no longer Titleist) basketball. Manufacturer:Product was m:1 and then changed to 1:1 behind the scenes. This is confusing for those learning about normalization. It seems the error was noticed while recording and fixed "off camera" - it would be helpful to correct the error in the video for those of us following along. I was confused about how having just the product name as a foreign key could uniquely identify both the product and manufacturer when, at that point, two manufacturers had basketballs.
@Kipviss3 жыл бұрын
niemand gaat dit lezen broer
@kaedien3 жыл бұрын
@@Kipviss behalve jou!
@jkirkwold5 ай бұрын
In the section explaining 2NF, when deduping the Product Table, you got rid of two rows. The first I understand (Bat, Louisville Slugger) because it was a duplicate. However, you also got rid of (Basketball, Titleist) even though it wasn't a duplicate. Why? Great video!
@lokmanboukhoulda44964 жыл бұрын
Thank you! the best explanation I have found on the net!!
@chojuj45335 ай бұрын
Very well explained
@basharatmir40253 жыл бұрын
Brilliant ,,,,,lecturer
@saltech20242 жыл бұрын
Your tutorials are of no doubt .... Kindly make video(s) on "Entity Diagrams"
@Hevletica2 жыл бұрын
I cannot thank you enough.
@LenaDobrinova3 жыл бұрын
1. Thanks for your video! 2. One of the "Basketball-SP" records under the "Products" table needs to be deleted. 3. Price for "Basketball-SP" needs to be updated in the original table ( @16:49). It should be either $23 or $25. 4. Order Totals for "Customer Order ID" #1 and #4 don't look correct ("Customer Orders" table).
@EphemeralMemory2 жыл бұрын
Great, concise video! Thank you
@michalroesler Жыл бұрын
Great video Joey.
@helovesdata84833 жыл бұрын
This is good. I'm new to this therefore, I'll need a week to design my first database...lol
@shubhamsharma-ne2ke2 жыл бұрын
awesome video. Great explanation.
@jenh31835 жыл бұрын
You're a great teacher - thanks for making this available to everyone.
@mohammadkashkooly19876 жыл бұрын
Joey, Thank you so much for helping us the little guys.
@uzairkhan89534 жыл бұрын
Really useful information. Helped me with my concepts. Thank you so much Joey.
@usmcpound5 жыл бұрын
Thanks so much for the informative video. This is much more clear and concise than the slides and book I've received from my database class.
@HerePiggyPiggy5 жыл бұрын
Your 2nd normal form needs composite keys for customer and product. Your “primary keys” fall apart the moment you get two customers with the same name or two basketballs from different manufacturers.
@renaissongsman5 жыл бұрын
Keep watching? That happened after about 20:00 ... but, yeah.
@kaedien4 жыл бұрын
This was fixed behind the scenes at 8:25. The Titleist basketball was deleted and Mark Smith's order was changed from Titleist to Spaulding.
@ruixue69555 жыл бұрын
4:19 2nd normal form 5:05 *partial dependence* 6:55 resolve partial dependency 9:45 3rd normal form 11:46 transitive dependency 13:51 fourth normal form 17:12 demo example 17:34 1.
@johnsonmuppasani22083 жыл бұрын
Excellent
@blaze1175 жыл бұрын
In 8:30 your product table contains basketball-Spaulding basketball- titleist and ypu just deleted basketball titleist and the supplier titleist supplying basketballs suddenly disappeared from the database. im quite confused there
@adityakolte25995 жыл бұрын
Having 2 basketball products in Product Table would no longer keep the Primary Key Unique
@nickbull72783 жыл бұрын
@@adityakolte2599 But he loses information by doing so - how can you know that Titleist produces basketballs? This is a bad choice of primary key. Clearly other manufacturers can produce basketballs, and manufacturers can produce more than one product. The solution would be a new product ID column, or a composite primary key of both columns. Thinking forward, a product ID would be better, as the same manufacturer could make the same product, with additionally added columns for e.g., descriptions (e.g., different colors, sizes)
@ReisQuarteu3 жыл бұрын
@@nickbull7278 The author corrected the above table in 8:36, so that basketballs are produced only by Spaulding in the simple example. That way, the 2NF was correctly applied. But you right: if two different manufactures can produce the same product, there was no dependency in the above table; therefore, the products table should not have been created.
@dylang97903 жыл бұрын
Thank you so much. your video is really useful for me
@kishorearr66392 жыл бұрын
love this one very much!!!!
@yahiabajbouj28183 жыл бұрын
Thanks for this video
@htji44 жыл бұрын
Thanks Joey, you're a great teacher.
@Devruwan5 жыл бұрын
Great explanation of the topic. Thank you for teaching us :)
@Adeshiomedia2 жыл бұрын
waw impressive
@umairjibran75 жыл бұрын
those who haven't watched this video and searching for "DB Normalization" are even dumber than I am. This is a Life saver.
@arnabpersonal67293 жыл бұрын
Maybe youtube is
@IrishDean10003 жыл бұрын
Thanks for this
@AusieGamer8342 жыл бұрын
That's how you explain normalisation.
@ekaterinavolkova4348 Жыл бұрын
Great! Thanx!
@hamedahmadi13822 жыл бұрын
thanks answered my question🙂
@dagmawihaddish32354 жыл бұрын
Pls tutor java,c#,assembly. Only one ofcourse. I only saying this b/c u helped me a lot thank you very much.
@justinemsquare8832 жыл бұрын
nice tutorial
@wehshijutt65374 жыл бұрын
Excellent job
@davidholguin62435 жыл бұрын
That was Excellent ! I guess I’ve been lucky with not having so complicated data. Thanks, Sgt. Dave
@markbrad1234 жыл бұрын
"Nothing but the key" An approximation of Codd's definition of 3NF, paralleling the traditional pledge to give true evidence in a court of law, was given by Bill Kent: "[every] non-key [attribute] must provide a fact about the key, the whole key, and nothing but the key".[7] A common variation supplements this definition with the oath: "so help me Codd".[8] Requiring existence of "the key" ensures that the table is in 1NF; requiring that non-key attributes be dependent on "the whole key" ensures 2NF; further requiring that non-key attributes be dependent on "nothing but the key" ensures 3NF. While this phrase is a useful mnemonic, the fact that it only mentions a single key means it defines some necessary but not sufficient conditions to satisfy the 2nd and 3rd normal forms. Both 2NF and 3NF are concerned equally with all candidate keys of a table and not just any one key.
@kanbisama3 жыл бұрын
Thank you so much for this video.
@johnesraelo46143 жыл бұрын
excellent work Joey
@mikesdailygaming2 жыл бұрын
Normalization might as well have been mandarin before now, thank you!
@dawitworku8213 жыл бұрын
Thank you a lot, you are different!
@adityagorre2 ай бұрын
In this video 20:16 how did you sort product key. if we double click on that will it save all the rows
@alemtewodros21315 жыл бұрын
I am the luckiest to be here.Thanks Sir
@marko-lazic4 жыл бұрын
But how are Dozen, Pack, Inch and $ atomic when they are combined with numbers?
@ironicxd69944 жыл бұрын
Thank you so much , this helped me a lot , keep it up plz
@brenthalbach36452 жыл бұрын
Great stuff. How would you deal with price changes over time? Do you need a separate Price table with dates or something? Would be great to get your input. Thanks, appreciate your content.
@GregoryKodolanyiRitter4 жыл бұрын
Great, thank you!
@jbighitter3 жыл бұрын
Bob Smith on bottom two rows changes to Bill Smith later
@michaelhunter48914 жыл бұрын
Our teacher showed us this video.
@jeetsoni6722 жыл бұрын
hows does the qualntity depend on the order date? Can we just notpull the quantities using customer id and product?
@happyjays7145 Жыл бұрын
I noticed that Product ID - Basketball - SP is duplicate in product tabke so it is not qualified as Primary Key...?
@nickt4234 жыл бұрын
@26:24 You have the OrderTotal for OrderID 1 as $70 (in the Customer Orders table) but didn't bsmith1 order two $70 products. Shouldn't the OrderTotal for OrderID 1(in the Customer Orders table) be $140?
@dafuq31224 жыл бұрын
same questions
@user-jz9rm8xn9n Жыл бұрын
ذاكر الكويز يابطل…
@brb2010ful Жыл бұрын
قاعدين نذاكر
@dosdeviant3 жыл бұрын
Glad I found this.
@chriskobee3563 жыл бұрын
From 33:00 min to 34:30: why didn't you create a many-to-'many relationship between "Customer" and for example a table "Email-subscription". Now it looks like you created the intermediate table "Customer Email Subscription" but left out the other side (table Email subscription) that holds all the different types of subscriptions. Idem dito for the Mail Catalog set up.
@perkjr7834 Жыл бұрын
How does product manufacturer depend on product if there is a manufacturer that has 2 diff products
@sulemanmasood13822 жыл бұрын
sir my db is in mysql using MYISAM.... No foreign keys implemented with some columns repeating in tables as well... i have approximatelly 40 tables and all containns approx 500 rows.... but 5 or 6 tables contains above one million rows each....db is not normalized.....but it is still working fine...on LAN and on cloud as well ... what will be fuiture of my db...
@stevenchen8074 жыл бұрын
Hi Joey, Thanks for the very instructional video. I do have a question. What do we do with the two ProductID Basketball-SP with different prices?
@steeleye20004 жыл бұрын
I think that was an oversight. They should either be the same price and then one of the rows would be deleted or the basketballs should be named to differentiate them (in the product column) like Basketball-yellow and Basketball-Orange.
@edgarsvilums15504 жыл бұрын
You just add a different Product ID for the differently priced one.
@LenaDobrinova3 жыл бұрын
one of 2 records needs to be deleted
@giorgiodealcantara83745 жыл бұрын
Thanks for the video, Joey! Pretty good explanation. I got with one doubt in the end. What is the PK for the Customer mail catalog and the customer email subscription tables?
@DNALectures3 жыл бұрын
In your second form. you have shown customer, product and order as composite key. in logical sense they does make composite key but in your example or the data you have shown only customer and product is making up a composite key.
@GoodDeedsLeadTo Жыл бұрын
2nd Normal form Why do we need order date to make a unique composite key, when customer and product are sufficient to make a primary key? Please answer the question, thanks
@iamreg196514 сағат бұрын
A Primary Key must be unique. Take away order date/order number from that key and one customer would only ever be allowed to buy a product once.
@NoWhiteGullibility5 жыл бұрын
Awesome
@ronyniv225 жыл бұрын
The best one that i have seen!!
@aroxing2 жыл бұрын
Assume you have a table User(id, email, username). All fields are unique. Does it satisfy 3NF?
@jetmartin95012 жыл бұрын
Great stuff! Very helpful. Not to be picky but in trying to understand the "solution" I noticed (in the original large table) that Bob Smith made two purchases on 8/9 and the Order Total didn't add up to the total of the two lines. The total in the chart is $70...shouldn't it be $60 or am I missing something? Also should the "Customer Email Subscriptions" and "Customer Mail Catalogs" tables be JOIN tables? It seems that there is a Many-to-Many relationship between these tables and Customers (e.g.,, Customers can subscribe to Many Email subscriptions and an Email subscription can belong to many Customers). Seems like the classic situation for a Join table. Also currently the way you have it defined there is no primary key for these Email and Mail tables (as there are duplicates). Not sure if that is an issue. Thoughts?
@prasanthrajappan44013 жыл бұрын
Do we need to split the Customer address in example 1 to make it in 1st normal form as address seems to be composite attribute?
@fatefulwall30105 жыл бұрын
Extremely helpful! Thank you Joey!!!
@kanduriveeresh95685 жыл бұрын
It was very well explained with example, thank you
@joylm91082 жыл бұрын
Could the customer order table be further normalised to the 4nf by pulling out the customer order and order date?
@fillerchatter76124 жыл бұрын
Just wondering have I wrote the SQL correctly for this? Many thanks, Robert CREATE DATABASE OrderLine /* Create this table 1st */ Create Table ProductManufacturers(ProductManufacturer varchar(50) Primary Key , ProductManufacturerAddress varchar(50)) Insert into ProductManufacturers(ProductManufacturer,ProductManufacturerAddress) values('Spaulding', '1 Spalding way') Insert into ProductManufacturers(ProductManufacturer,ProductManufacturerAddress) values('Louisville Slugger', '345 Slugger Avenue') Insert into ProductManufacturers(ProductManufacturer,ProductManufacturerAddress) values('Rawlings', '23 Rawlings Court') Insert into ProductManufacturers(ProductManufacturer,ProductManufacturerAddress) values('Titleist', '1234 Titlest Road') /* Create this table 2nd */ Create Table CustomerEmailSubscription(CustomerID varchar(100) NOT NULL, CustomerEmailSubscriptions varchar (100), Primary Key(CustomerID,CustomerEmailSubscriptions)) Insert into CustomerEmailSubscription(CustomerID,CustomerEmailSubscriptions) values('bsmith1', 'Baseball') Insert into CustomerEmailSubscription(CustomerID,CustomerEmailSubscriptions) values('bsmith1', 'Basketball') Insert into CustomerEmailSubscription(CustomerID,CustomerEmailSubscriptions) values('jthomas1', 'Baseball') Insert into CustomerEmailSubscription(CustomerID,CustomerEmailSubscriptions) values('bsmith2', 'Golf') /* create this table 3rd */ Create Table CustomerMailCatalogs(CustomerID varchar(100), CustomerMailCatalogs varchar(100), Primary Key(CustomerID,CustomerMailCatalogs)) Insert into CustomerMailCatalogs(CustomerID,CustomerMailCatalogs) values('bsmith1', 'Baseball') Insert into CustomerMailCatalogs(CustomerID,CustomerMailCatalogs) values('bsmith1', 'Basketball') Insert into CustomerMailCatalogs(CustomerID,CustomerMailCatalogs) values('jthomas1', 'Baseball') Insert into CustomerMailCatalogs(CustomerID,CustomerMailCatalogs) values('bsmith2', 'Baseball') /*Create this table 4th*/ Create Table Customers(CustomerID varchar(100) Primary Key, FirstName Varchar(100), Surname Varchar(100), CustomerAddress varchar(100), CustomerEmail varchar(100)) Insert into Customers(CustomerID, FirstName,Surname,CustomerAddress,CustomerEmail) values ('bsmith1','Bob', 'Smith', '123 Broadway', 'bsmith@gmail.com') Insert into Customers(CustomerID, FirstName,Surname,CustomerAddress,CustomerEmail) values ('jthomas1','Jill', 'Thomas', '12 Cockland grove', 'jthomas@gmail.com') Insert into Customers(CustomerID, FirstName,Surname,CustomerAddress,CustomerEmail)values ('bsmith2','Jill', 'Thomas', '5 Maple Street', 'smith5@hotmail.com') /*Create this table 5th*/ Create Table CustomerOrders(CustomerOrderID int Primary Key identity(1,1), CustomerID varchar(100) references Customers(CustomerID), OrderDate Date, OrderTotal Float) Insert into CustomerOrders(CustomerID,OrderDate,OrderTotal) values('bsmith1','8/9/2020', 70) Insert into CustomerOrders(CustomerID,OrderDate,OrderTotal) values('jthomas1','8/10/2020', 57) Insert into CustomerOrders(CustomerID,OrderDate,OrderTotal) values('bsmith1','8/10/2020', 23) Insert into CustomerOrders(CustomerID,OrderDate,OrderTotal) values('bsmith2','8/10/2020', 88) /*Create this table 6th*/ Create Table Products(ProductID VarChar(50) Primary Key, Product Varchar(50), ProductManufacturer Varchar(50) references ProductManufacturers(ProductManufacturer), ProductDetails Float, ProductCost Float) Insert into Products(ProductID,Product,ProductManufacturer,ProductDetails,ProductCost) values('BasketBall-SP', 'Basketball','Spaulding',29.5, 25) Insert into Products(ProductID,Product,ProductManufacturer,ProductDetails,ProductCost) values('Bat-L', 'Bat','Louisville Slugger',33, 35) Insert into Products(ProductID,Product,ProductManufacturer,ProductDetails,ProductCost) values('Softball-R', 'Softball','Rawlings',4, 6) Insert into Products(ProductID,Product,ProductManufacturer,ProductDetails,ProductCost) values('Bat-R', 'Bat','Rawlings',32, 45) Insert into Products(ProductID,Product,ProductManufacturer,ProductDetails,ProductCost) values('Golfballs-T', 'Golf Balls','Titleist',12, 44) Insert into Products(ProductID,Product,ProductManufacturer,ProductDetails,ProductCost) values('Basketball-T', 'Basketball','Titleist',12, 44) /* Create this table 7th */ drop Table CustomerOrderLines create Table CustomerOrderLines(ProductID varchar(50), CustomerOrderID int, quantity int, Primary Key(ProductID,CustomerOrderID), Foreign Key(ProductID) references Products(ProductID), Foreign Key(CustomerOrderID) references CustomerOrders(CustomerOrderID)) Insert into CustomerOrderLines(ProductID,CustomerOrderID,Quantity) values('Basketball-SP',1,1) Insert into CustomerOrderLines(ProductID,CustomerOrderID,Quantity) values('Bat-L',1,1) Insert into CustomerOrderLines(ProductID,CustomerOrderID,Quantity) values('Softball-R',2,2) Insert into CustomerOrderLines(ProductID,CustomerOrderID,Quantity) values('Bat-R',2,1) Insert into CustomerOrderLines(ProductID,CustomerOrderID,Quantity) values('GolfBalls-T', 4, 2) Insert into CustomerOrderLines(ProductID,CustomerOrderID,Quantity) values('Basketball-T', 4, 2) select* FROM CustomerEmailSubscription select * from ProductManufacturers select * from Products select * from Customers
@gooon6663 жыл бұрын
Isn't the Order Total field a Calculated field? Can it have a place in a table? If yes, how was it calculated here to show the results it exhibits here? Newbie here, thank you :)
@sukanyachauhan96535 жыл бұрын
Joey, please help with the download link for SQL server. I am starting SQL learning from your video.
@osmankhaled45655 жыл бұрын
Excellent Video.
@nyanyaa80434 жыл бұрын
Hi Joey, Do you offer training beside the online videos? you are good at this.
@dafuq31224 жыл бұрын
Hi sir for the 8:30 part the basketball are spaulding and Titleist, but where is the Titleist after u delete those stuff, and the customer order twice, then the price should be 2x isn't it? but when you separated it, it is still the same price for one, I am confused. By the way thanks for the video😊😊😊.
@vasilis84886 жыл бұрын
@Joey Blue Thank you for your videos. They are very helpful. Now about this specific video. Is it necessary to have a separate Customer order lines table? If we had an orders table with the product id as a 2nd FK and the quantity, wouldn't we also be in 4NF?
@joeyblue15 жыл бұрын
It all depends on what else you are storing in the orders table. Many times there are things that you want to store at the Order level. Maybe a flat Handling Fee that doesn't depend on the Product. You would need to figure out where to store that information without repeating it on every product line. There are many ways to do it, you just want to keep in mind the grain of the table and if you are unnecessarily repeating data.
@a7md944 Жыл бұрын
I am not sure, but I think 4NF is different than the example is shown. Anyway, thank you
@AggTheMag2 жыл бұрын
which application are you using for this lesson?
@Martin-lf9se5 жыл бұрын
Nicely done Joey! Thank you...
@nolanhartwick48626 жыл бұрын
This video is quite good. It would be great if you could keep doing more of these Database theory videos.
@helheimrgaming25476 жыл бұрын
Thank you Joey, very helpful!
@kaym23325 жыл бұрын
In the example for third normal form where you break out product manufacturer and adress to avoid redundancy and then declare manufacturer as foreign key in the original table, does that still not result in redundancy in the first table? The column of Product Manufacturer that you colored as foreign key still seems to have repeating values in the rows. I know the transitivity has been dealt with though. Happy if somebody could explain this for me.
@TakingItCasual5 жыл бұрын
It is not possible (at least in this case) to completely eliminate redundancy. The goal is merely to reduce redundancy. The main goal in any case was to make it so a manufacturer's address is only specified in one place. Instead of repeating both the manufacturer and its address, it's much better to just repeat the manufacturer.