Database Design Step-By-Step Beginner Tutorial Using SQL Server

Подписаться 7 тыс.

Просмотров 73 тыс.

50% 1

If the background music bothers you go here: • Database Design Step-B...
INSTAGRAM: links.thedevlife.co/instagram...
DISCORD: links.thedevlife.co/discord/t...
FACEBOOK: links.thedevlife.co/facebook/...
In this installment of the API Series, we share the process of designing a database for a new design in SQL Server. Using SQL Server Management Studio ( SSMS ), we provide a step-by-step guide to database design.
Database design is the foundation of any application that manipulates or has dependencies on data and/or databases. This video is a must if you ever want to build an API ( REST API ) as a developer to support an application, whether that is a mobile application or web application.
Videos Included in the Web API Series
1. Virtual PC Setup (VirtualBox) Working Environment • How To Create a Virtua...
2. Installing SQL Server Express • How To Install SQL Ser...
3. Database design (this video)
4. EF Core (Database First) & API CRUD • Web API Entity Framewo...
0:00 - Intro
0:17 - About the channel (don't forget to subscribe)
0:54 - Database design process outline
1:59 - Diagram the necessary database entities needed
20:02 - Create the new database using SSMS (SQL Server Management Studio)
33:25 - Inserting new test data
39:21 - Conclusion
#sql #database #thedevlife

Наука

Опубликовано:

26 июл 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 76

@thedevlife 7 месяцев назад

You might also be interested in learning the top reasons why self-taught developers fail -> ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE--_OQ8h9ts80.htmlsi=9AZSIkZckVszMfCA

@robinq5511 2 года назад

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!

@thedevlife 2 года назад

I appreciate it. Thank you for the support.

@ronaldodiaz8770 2 года назад

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 !

@thedevlife 2 года назад

I’m glad it was helpful 👍

@data9051 2 года назад

Thanks for this awesome quick video. Just did my first database design and creation.

@guillermomorrison3846 2 года назад

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 2 года назад

Thank you 🙏

@3SA627 2 года назад

precious content,many thanks!

@ladefected4475 2 года назад

That was fun.... Very well done presentation! Thx.

@thedevlife 2 года назад

Thank you.

@toupocallen7572 2 года назад

I love your videos. Please keep making them.

@thedevlife 2 года назад

thank you. I appreciate the support.

@davisward3144 3 года назад

great video, appreciate it!

@thedevlife 3 года назад

Thank you. I’m glad you found it helpful 👍

@daretosucceed 3 года назад

Waiting for next

@Naveedqureshi 2 года назад

I don't usually comment on videos but this one is the the masterpiece.... Superb man 👍 great explanation.

@thedevlife 2 года назад

I'm really humbled by this. I appreciate the support and I'm glad you found the video helpful.

@joaquinperez8657 2 года назад

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

@thedevlife 2 года назад

I’m happy to hear that 👍

@Kikikuku2 3 месяца назад

The video was very helpful, many thanks!

@thedevlife 3 месяца назад

I’m very glad. The reason why I keep creating videos. Thanks for your support.

@nguyenhongson3593 2 года назад

Thanks. Your Video is very useful. It's helped me understand more about how to use Databases in SQL.

@thedevlife 2 года назад

Thank you. I’m glad I was able help 🙏

@bonkeselemani503 3 года назад

Very informative, thanks a lot

@thedevlife 3 года назад

Thank you. I'm glad it was useful.

@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 RU-vid videos regarding database design but you made it so easy to understand. Thanks for the video!

@thedevlife Год назад

Noted, not the first time I hear this. I am contemplating re-rendering the video without the background music.

@sagarhande2906 2 года назад

Very informative and well explained 👏👍

@thedevlife 2 года назад

thank you. I’m glad you found value.

@daretosucceed 3 года назад

I am going to Bookmark this playlist

@thedevlife 3 года назад

Thank you, the new video should be out in the coming week.

@JeffersonCanedo 2 года назад

Thankyou very nice video I needed this

@thedevlife 2 года назад

you are welcome. I'm glad you found the video useful.

@alfredkalinga466 3 года назад

great video for learning

@thedevlife 3 года назад

Thank you, I’m glad you found the video useful.

@basswellbiotech 2 года назад

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..

@kokebzerai2807 3 года назад

Thank you so much this step by step instruction very popular method. I hope you will come with more courses.

@thedevlife 3 года назад

I’m glad you found it useful and yes I will publish new tutorials.

@kokebzerai2807 3 года назад

@@thedevlife Thank you sir and I will be one of your bonafide students.

@rai_976 2 года назад

Thanks for your video

@thedevlife 2 года назад

You are welcome 🙏

@joeyzalman8254 3 года назад

great explanation

@thedevlife 3 года назад

Thank you, that means a lot.

@zbmat6353 3 года назад

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 !

@thedevlife 3 года назад

Thanks for catching that and I appreciate the support.

@laronantungwana9934 9 месяцев назад

please make this into a series,its helping us new analysts.

@thedevlife 9 месяцев назад

What do you think the next episode should cover?

@laronantungwana9934 9 месяцев назад

@@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.

@nelvinmathew2516 2 года назад

Nice vedio and informative 👍

@thedevlife 2 года назад

Thank you

@DesignDensity 5 месяцев назад

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.

@thedevlife 5 месяцев назад

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.

@DesignDensity 5 месяцев назад

@@thedevlife Thanks for your detailed explanation. It now makes clearer sense and I totally agree with you :)

@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...

@thedevlife Год назад

Thank you 🙏 I’ve been looking for suggestions for the next videos. I will certainly consider your request 👍. Thanks for your support.

@sivakrishna3550 Год назад

@@thedevlife thank your for your consideration and taking time to respond 👍

@benjie2968 2 года назад

3:55 This is me😅. Subcribed! 😎

@thedevlife 2 года назад

Thank you for the support.

@DiviPhotos 3 года назад

Very nice video

@thedevlife 3 года назад

Thank you. I appreciate it. So far, this has been the longest video I've released.

@madie2659 Год назад

Great video but music is a bit distracting

@nickt423 3 года назад

@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?

@alfredclausen2593 2 года назад

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.

@ttu-lb3mx 2 года назад

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.

@thedevlife 2 года назад

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 🙏

@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

@thedevlife Год назад

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.