You might also be interested in learning the top reasons why self-taught developers fail -> th-cam.com/video/-_OQ8h9ts80/w-d-xo.htmlsi=9AZSIkZckVszMfCA
This video is exactly what I was looking for. I needed to see someone's design process from conceptual to logical to physical. Awesome video man thank you !
Awesome video. Very well explained end-to-end database design. Just one small suggestion : please don't add background music while you are explaining, it makes it difficult to concentrate on the content. Apart from that, you explained the whole thought process so well that everything was clear for me in one go, I have watched many TH-cam videos regarding database design but you made it so easy to understand. Thanks for the video!
I personally think the "Cars" table should have been called the "CarAds" or "CarItems" or "CarListing" table because this is what the user mostly interacts with from the frontend side, this gives it a distinct name which is easy to understand 😊😊 The "Makes" should read "CarMarks" and the same for Models > "CarModels", this makes things easier at first glance. Overall enjoyed the video, thank you for this tutorial.
I agree with renaming the table “Makes” to “CarMakes” or “CarManufacturers”. I don’t agree with renaming the “Cars” table to anything else, not saying you are wrong, but I wouldn’t do it, here is why: if in the future I need to create a table that contains car listings or a table that holds Ads (advertisements) for cars. The “Cars” table represents a car as an entity. I do see the advantage of making it clear to understand what the table holds, but as rule I always try to break down objects down to entity representations which makes it easier to build relationships with other tables. Thanks for your feedback.
This series looks like it will be useful for me, coming from a database model using DBF tables. Your approach makes it much easier to understand the transition than most SQL tutorials. I really appreciate that!
great video on a design framework for database design. Just started learning SQL and love seeing how the learning I'm doing coincides with your database design.
@@thedevlife I would appreciate a project from start to finish just showing how to apply all the information we have learnt. From creating the database to pulling information out,to cleaning the data and visualising it either with power I,tableau or python.
This hands-on explanation is amazing, I can't find the continuation of this video on building relationships and constraints, please help me to find one, if haven't made one, please do whenever you can!! Thanks...
38:34 a small correction...In the "Models" table you had to enter "Civic" instead of "Honda"... Great work touching explaining from ground up...Keep going !
awesome videos, great explanations. Thank you for taking the time to prepare and do this video, it helped me a lot. I am building my own website. I had paid three developers that they did not do the database, thus I am doing it myself. It worked.... Yes!...sir
Thank you very much for your video, Francisco. Respectfully, please allow me to make a technical observation. The focus of a tutorial video such as this one is to impart knowledge. Personally, I found it difficult to concentrate on the content of your information because of the accompanying background music. Information worth listening to will always stand up on its own. Nonetheless, if you believe that music is a necessary component of your work product, please consider greatly lowering the volume of the music or selecting a softer arrangement. Again, I am simply making a good faith personal observation. Others may not share my opinion. Thank you again for your tutorial and for listening to my comment.
Thank you for the feedback. It’s not the first time I hear this suggestion and I’ve taking it into consideration. In newer videos I made made sure the music is turned down a lot more. I appreciate you pointing that out 🙏
7:56, why do you need the extra make table? you said it was to prevent miss spellings but you would always give the user a pre-set of selection so that wouldn't be a problem as the name wouldn't be misspell, so what are the benefits really? also you would have repeated make data but you would also end up repeating the id from the table instead of the make so that also doesen't matters. The only reason that make sense is that int takes less space than string but you are creating an entire table vs a simple string column. thank you for your answer
Great question, thanks for watching the video. This is a level of data normalization. Yes, storage is one benefit I am creating a new table with a handful of records, if you end up with a parent table with a million records as you mentioned an int will save storage. It also allows for expansion in your application. Let's say that in the future you don't want to allow Ford to be selected from a dropdown, you can add a column to the child table (makes) to control whether values/options are displayed or not. The best practice rule is that if you will have a column/field in a table that could hold many records and there is a small variations of values compared for that particular field, you should break that up into a child table. In the long run this will help with performance while querying a large number of records.
@9:32, in the cars table, wouldn’t the MakeID be dependent on the ModelID, and the ModelID is dependent on the CarID? Thats means Make_ID is transitively dependent on Car_ID. If thats the case then that table is not in the 3rd normal form, right?
In my company, we usually entered both values in the same table like this Field1|Field2|Active|Timestamp|EnteredBy Honda|CRV|1|MMDDYYYY:HH...|John Doe Honda|Civic|1|MMDDYYYY...|Jane Doe Then in the Database, you make a lookup on the make, something like this. Give me distinct records on field1 where Active =1 in a list box. This would give me all active car makes in one long list. And another list box for the model. Give me all records for Field2 where Field1 = the model selected in the first list box, and Active = 1 I find this easier than using two separate tables.
You might also be interested in learning the top reasons why self-taught developers fail -> th-cam.com/video/-_OQ8h9ts80/w-d-xo.htmlsi=9AZSIkZckVszMfCA
Excellent video. Explained in simple terms in a calm cool tone. I look forward to the foreign key video........thanks!
Thanks for requesting that video. I will surely get it out there.
This video is exactly what I was looking for. I needed to see someone's design process from conceptual to logical to physical. Awesome video man thank you !
I’m glad it was helpful 👍
Awesome video. Very well explained end-to-end database design. Just one small suggestion : please don't add background music while you are explaining, it makes it difficult to concentrate on the content. Apart from that, you explained the whole thought process so well that everything was clear for me in one go, I have watched many TH-cam videos regarding database design but you made it so easy to understand. Thanks for the video!
Noted, not the first time I hear this. I am contemplating re-rendering the video without the background music.
Thanks for this awesome quick video. Just did my first database design and creation.
I personally think the "Cars" table should have been called the "CarAds" or "CarItems" or "CarListing" table because this is what the user mostly interacts with from the frontend side, this gives it a distinct name which is easy to understand 😊😊
The "Makes" should read "CarMarks" and the same for Models > "CarModels", this makes things easier at first glance.
Overall enjoyed the video, thank you for this tutorial.
I agree with renaming the table “Makes” to “CarMakes” or “CarManufacturers”. I don’t agree with renaming the “Cars” table to anything else, not saying you are wrong, but I wouldn’t do it, here is why: if in the future I need to create a table that contains car listings or a table that holds Ads (advertisements) for cars. The “Cars” table represents a car as an entity. I do see the advantage of making it clear to understand what the table holds, but as rule I always try to break down objects down to entity representations which makes it easier to build relationships with other tables. Thanks for your feedback.
@@thedevlife Thanks for your detailed explanation. It now makes clearer sense and I totally agree with you :)
Great video but music is a bit distracting
This series looks like it will be useful for me, coming from a database model using DBF tables. Your approach makes it much easier to understand the transition than most SQL tutorials. I really appreciate that!
I appreciate it. Thank you for the support.
great video on a design framework for database design. Just started learning SQL and love seeing how the learning I'm doing coincides with your database design.
Thank you 🙏
please make this into a series,its helping us new analysts.
What do you think the next episode should cover?
@@thedevlife I would appreciate a project from start to finish just showing how to apply all the information we have learnt. From creating the database to pulling information out,to cleaning the data and visualising it either with power I,tableau or python.
This hands-on explanation is amazing, I can't find the continuation of this video on building relationships and constraints, please help me to find one, if haven't made one, please do whenever you can!! Thanks...
Thank you 🙏 I’ve been looking for suggestions for the next videos. I will certainly consider your request 👍. Thanks for your support.
@@thedevlife thank your for your consideration and taking time to respond 👍
The video was very helpful, many thanks!
I’m very glad. The reason why I keep creating videos. Thanks for your support.
I don't usually comment on videos but this one is the the masterpiece.... Superb man 👍 great explanation.
I'm really humbled by this. I appreciate the support and I'm glad you found the video helpful.
38:34 a small correction...In the "Models" table you had to enter "Civic" instead of "Honda"... Great work touching explaining from ground up...Keep going !
Thanks for catching that and I appreciate the support.
awesome videos, great explanations. Thank you for taking the time to prepare and do this video, it helped me a lot. I am building my own website. I had paid three developers that they did not do the database, thus I am doing it myself. It worked.... Yes!...sir
I’m happy to hear that 👍
Thank you very much for your video, Francisco. Respectfully, please allow me to make a technical observation. The focus of a tutorial video such as this one is to impart knowledge. Personally, I found it difficult to concentrate on the content of your information because of the accompanying background music. Information worth listening to will always stand up on its own. Nonetheless, if you believe that music is a necessary component of your work product, please consider greatly lowering the volume of the music or selecting a softer arrangement. Again, I am simply making a good faith personal observation. Others may not share my opinion. Thank you again for your tutorial and for listening to my comment.
Thank you for the feedback. It’s not the first time I hear this suggestion and I’ve taking it into consideration. In newer videos I made made sure the music is turned down a lot more. I appreciate you pointing that out 🙏
7:56, why do you need the extra make table? you said it was to prevent miss spellings but you would always give the user a pre-set of selection so that wouldn't be a problem as the name wouldn't be misspell, so what are the benefits really? also you would have repeated make data but you would also end up repeating the id from the table instead of the make so that also doesen't matters. The only reason that make sense is that int takes less space than string but you are creating an entire table vs a simple string column. thank you for your answer
Great question, thanks for watching the video. This is a level of data normalization. Yes, storage is one benefit I am creating a new table with a handful of records, if you end up with a parent table with a million records as you mentioned an int will save storage. It also allows for expansion in your application. Let's say that in the future you don't want to allow Ford to be selected from a dropdown, you can add a column to the child table (makes) to control whether values/options are displayed or not. The best practice rule is that if you will have a column/field in a table that could hold many records and there is a small variations of values compared for that particular field, you should break that up into a child table. In the long run this will help with performance while querying a large number of records.
I am going to Bookmark this playlist
Thank you, the new video should be out in the coming week.
3:55 This is me😅. Subcribed! 😎
Thank you for the support.
That was fun.... Very well done presentation! Thx.
Thank you.
I love your videos. Please keep making them.
thank you. I appreciate the support.
Very informative, thanks a lot
Thank you. I'm glad it was useful.
Thanks. Your Video is very useful. It's helped me understand more about how to use Databases in SQL.
Thank you. I’m glad I was able help 🙏
Did you later make a video on creating relationships between the tables?
I haven’t yet 😅
@@thedevlifecome on man, it's been 3years so giddy up 😩😅😅.
Really like the way you explain stuff clearly 👍
Waiting for next
Thankyou very nice video I needed this
you are welcome. I'm glad you found the video useful.
Thanks for your video
You are welcome 🙏
@9:32, in the cars table, wouldn’t the MakeID be dependent on the ModelID, and the ModelID is dependent on the CarID?
Thats means Make_ID is transitively dependent on Car_ID. If thats the case then that table is not in the 3rd normal form, right?
In my company, we usually entered both values in the same table like this
Field1|Field2|Active|Timestamp|EnteredBy
Honda|CRV|1|MMDDYYYY:HH...|John Doe
Honda|Civic|1|MMDDYYYY...|Jane Doe
Then in the Database, you make a lookup on the make, something like this.
Give me distinct records on field1 where Active =1 in a list box. This would give me all active car makes in one long list.
And another list box for the model.
Give me all records for Field2 where Field1 = the model selected in the first list box, and Active = 1
I find this easier than using two separate tables.
This is amazing sir, very clear and easy to follow step..... Where can i find the continuation to this video??... Ps am going to subscribe right now..
precious content,many thanks!
Very informative and well explained 👏👍
thank you. I’m glad you found value.
great video for learning
Thank you, I’m glad you found the video useful.
Thank you so much this step by step instruction very popular method. I hope you will come with more courses.
I’m glad you found it useful and yes I will publish new tutorials.
@@thedevlife Thank you sir and I will be one of your bonafide students.
great video, appreciate it!
Thank you. I’m glad you found it helpful 👍
Nice vedio and informative 👍
Thank you
Just a positive note - It’s unnecessary BGM and disruptive
Thanks for pointing it out, I did re-edit with no music, link in the description.
Very nice video
Thank you. I appreciate it. So far, this has been the longest video I've released.
great explanation
Thank you, that means a lot.
The video so helpful , the music so annoying
I heard that before, I re-edited the video th-cam.com/video/qCIFuoN32cM/w-d-xo.html
oh that great thank you @@thedevlife
.