Database Design for an Online Course Website

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

Просмотров 3,8 тыс.

50% 1

📝 Bonus PDF: This ERD, descriptions of each table and column with sample data, and SQL scripts to create all of the tables on your own database: www.databasestar.com/dbdesign...
🎓 Learn how to design an effective database and create it using SQL: databasestar.mykajabi.com/edd...
An online course website, such as Udemy or Pluralsight, will let students enrol in courses, complete lessons within the courses, and take quizzes.
In this video, you'll see how to design a database for an online learning management or online course system. We'll go through a range of requirements one by one, and create a database design (Entity Relationship Diagram) from scratch, getting to a diagram that meets all of the requirements.
⏱ TIMESTAMPS:
00:00 - Start our diagram
01:32 - Requirement 2
01:48 - Requirement 3
02:06 - Requirement 4
02:40 - Requirement 5
03:06 - Requirement 6
03:32 - Requirement 7
04:20 - Requirement 8
04:56 - Requirement 9
07:10 - Requirement 10
07:59 - Requirement 11
08:19 - Requirement 12
09:18 - Requirement 13

Наука

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

23 июл 2024

Ссылка:

Скачать:

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

Добавить в:

Мой плейлист

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

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

@judaperez681 2 месяца назад

I was exploring your youtube content... NEW SUB!

@DatabaseStar 2 месяца назад

Thanks! Glad you like it.

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

i struggle a lot designing a database. These videos are really helpful.

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

Glad you like them!

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

Just leaving a comment so that more people might see this. Let's go DB fellows. :D

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

Thanks!

@judaperez681 2 месяца назад

The video I was looking for

@DatabaseStar 2 месяца назад

Good to hear!

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

Exactly what was looking for

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

Thanks!

@Aacadian-xe8kq 7 месяцев назад

Amazing content, thank you for this upload 👍👍👍

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

Glad you enjoyed it!

@vannakvy9109 16 дней назад

Thanks for the great video.

@DatabaseStar 16 дней назад

Glad you liked it!

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

Amazing. Thank you

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

Glad you liked it!

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

you videos help me a lot. Im trying to start learning database design, and this channel is the best channel I can find, thx for videos, can you make a video about testing performance of database? (like put random data and stress)

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

Good to hear! Sure, I can make a video on that. Is there anything specific you want to know or see with testing the performance of a database?

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

Nice job👌

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

Thanks!

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

We need database design for cricket management along with their contracts, clubs, domestic structure etc

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

Good idea! I have a "sports league" on my list of future topics so I'll create one specific for cricket.

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

@@DatabaseStar I hope it will be your next video.

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

I think the quiz should be related to the module instead of the course. By relating the quiz to the course, you won't be able to set the quiz in a specific module. One module may have one or more lecture and/or one or more quizzes.

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

That's a good point. We can change it to relate the quiz to a module.

@CynicalSaint48 4 месяца назад

Thanks for the videos! Question I have never been able to find an answer to: Many simple tables versus Few complex tables. In this design, a 10 question quiz would have a Quiz table, 10 question tables, 10 correct answer tables, and 30 wrong answer tables. This results in 51 total tables in the database for a single quiz. Alternately, the quiz table could contain fields for the question id, question text, correct answer and 3 wrong answers, and then that table would have 10 entries. I am curious whether there are benefits of one or the other, or if it is just down to preference? Thanks again!

@DatabaseStar 4 месяца назад

Good question! If you have a quiz with 10 questions, you would only need the three tables: one for quiz, one for quiz_question, and one for quiz_answer. Each table should usually represent an object or entity, so you shouldn't need 10 different question tables - you would have 1 table for all 10 questions. Same for answers: you could have 1 answer table to contain all answers, and an indicator to show if it is correct or not. Generally fewer tables is better, but there needs to be enough so that the data quality is maintained and it's easy to make changes in one place.

@CynicalSaint48 4 месяца назад

@@DatabaseStar Thanks, I follow now. Think I was just a bit thrown by the Lucid representation of the tables. Thanks for answering the many versus few tables question too!

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

You miss the review table in this Diagram and also course category is also important

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

That’s true, we can add those concepts into this diagram to add those features.

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

Your video is excellent; it's exactly what I was looking for. Currently, I'm working on an e-learning platform, and I'd like to know how to create the admin section and a table for the teacher. On my platform, there are paywalls to allow students access via a monthly or annual subscription. How can I develop this section, and what suggestions do you have to implement it?

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

Thanks! I don't have any specific suggestions, but I would say you can try to list down your requirements as sentences and then update the database design. For example, "a course has a teacher, and a teacher can teach many courses". This may mean you have a teacher table, and a foreign key from the course table to the teacher table.

@longn.8804 7 месяцев назад

Hello Ben. Thanks for your video. It's very helpful and awesome. I've got a question for you: In each table, there is a PK usually being "id", e.g. the "Course" table has the "id" field and the "Student" table has another "id" field. I totally understand that these "id" fields specifically refer to their corresponding tables. However, does it make duplicate field names (as far as I read somewhere)? Should we keep them identical like that (all "id" fields) or should we make them unique, for example, student_id in the Students table, course_id in the Course table, etc.? Thank you in advance.

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

Thanks, I'm glad you like the video! Good question. The main problem I see with having all fields called "id" (like I usually do) is that if you select from multiple tables, then there will be many ID fields shown and it can be hard to see what the ID represents (e.g. is the lesson ID or the course ID). You can use column aliases to work around this. Using a more descriptive column name, such as student_id or course_id as you suggested, is another approach - and I think it's probably the better approach as it's clearer what it represents in large queries and it matches the foreign key names. I didn't use this approach in this design but perhaps I should in future designs. I would suggest being consistent though - pick one approach and use it throughout your design.

@longn.8804 7 месяцев назад

@@DatabaseStar Thanks for your explanation! Appreciate it!

@DuyNguyen-ti1ky 7 месяцев назад

How can I get the pdf file which contains full content and diagram?

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

It's on the page mentioned in the description: www.databasestar.com/dbdesign/

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

❤

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

Thanks!

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

I have a question please, wouldn't that join table have a primary key?

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

Yes, the joining tables could have a primary key to ensure they can be easily referenced and ensure they are unique. This could either be a combination of both FK columns, or a separate ID column.

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

@@DatabaseStar Thank you.