How to make Relations for Instructor Schedule(one to many and many to many between tables)

  • Problem

    How to make database design for Instructor Schedule(only relations between every table and other one to many AND Many to Many)

    Tables already created but relation not make (Section,Class,Instructor,Courses,Student)

    I need to make Tables Relation for Instructors schedule working in Training center give courses for Microsoft products

    as ACCESS ,EXCEL,C#,SQL as following

    * Training center Have more instructors .

    * Every instructor give more courses in ACCESS ,EXCEL,C#,SQL weekly from Sunday to Thursday .

    * Every instructor give Courses ACCESS ,EXCEL,C#,SQL in more classes inside Training center .

    *Training center have 10 classes and every courses can given in more classes within week .

    *Every courses ACCESS ,EXCEL,C#,SQL can given by more instructor .

    *Every instructor give more sections .

    * Section mean group of student every group of student classified to A,B,C,D,E,F.

    * Every section can given by more instructor within week .

    * Every section can given more courses in week .

    * Every section can get more courses in more classes .

    So that i need to know

    Instructor Michel give Courses C# And SQL from time 2 to time 4 Every Sunday And Wednesday weekly in class A1 And B1 And C1

    For section A And B and C And D (Relation between each table and others)

  • This is a homework assignment. I know, I did it when I studied too. Do your own homework. =)

  • Can you tell me this is true or not

    I do as following

    Courses and instructors many to many

    class and instructors many to many

    class and sections many to many

    are this relation true

    I already doing that but i need to sure that i make true

    Are relation above correct

  • I only need relations only to create schedule for instructors

    between tables mentions

  • I already posted image of my design in image above

    can you tell me this is correct or not

  • What is "true" or not depends on your business rules.

    The easiest way to do this is one relation at a time in your ERD. If you don't know how to draw an ERD, you're in over your head.

  • Only i need to know what

    you mean one relation at time

    I think you mean get CourseID,InstractorID,ClassID,SectionID

    in one table

  • Sounds like you either didn't do any relational theory in class or you didn't ever read the homework assignments. This is database design 101.

  • Why not need to answer the question I think you dont know and only talking

  • This is one of the classic schoolbook databases to learn database design. Maybe you should read one?

  • This was removed by the editor as SPAM

  • Thank you for reply

    yes it is easy solution for schedule

    but if i need to make my database for attendance student or attendance instructors

    this meaning create new database or what

  • No need for a new database but you do need to analyse the relationships and the entities.

    😎

    Start with a verbal analysis such as:

  • An Instructor(Person) has Zero or more Classes in Instructor_Class
  • An Instructor(Person) has Zero or more Courses in Instructor_Course
  • Each Course(Activity Group) has one or more Instructor(Person) in Instructor_Course
  • Each Class(Schedule) has one and only one Instructor(Person) in Instructor_Class
  • Each Class(Schedule) has one or more Student in Student_Class
  • Each Student(Person) has Zero or more Classes in Student_Class
  • Each Student(Person) has one and only one Section(Organization) in Student
  • Each Section(Organization) has one and only one Department in Section
  • Then the modelling will be straight forward.

  • Yes i do as this actually but how to make schedule for instructor collect

    instructor,course,class,section in one table

    please help me in that

    my design is

    and schedule for instructor as following

  • Viewing 15 posts - 1 through 15 (of 20 total)

    You must be logged in to reply to this topic. Login to reply