@ronaldodiaz8770
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 !
@iam_kundan
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 YouTube videos regarding database design but you made it so easy to understand. Thanks for the video!
@joegodindata
Thanks for this awesome quick video. Just did my first database design and creation.
@MoGrace2u-og
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!
@guillermomorrison3846
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.
@jeff.thecoder
Excellent video. Explained in simple terms in a calm cool tone. I look forward to the foreign key video........thanks!
@zbmat6353
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 !
@sivakrishna3550
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...
@rafacancode
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
@DesignDensity
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.
@laronantungwana9934
please make this into a series,its helping us new analysts.
@Kikikuku2
The video was very helpful, many thanks!
@Naveedqureshi
I don't usually comment on videos but this one is the the masterpiece.... Superb man 👍 great explanation.
@joaquinperez8657
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
@nickt423
@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?
@benjie-edr
3:55 This is me😅. Subcribed! 😎
@toupocallen7572
I love your videos. Please keep making them.
@nguyenhongson3593
Thanks. Your Video is very useful. It's helped me understand more about how to use Databases in SQL.
@ladefected4475
That was fun.... Very well done presentation! Thx.
@thedevlife