Results 1 to 3 of 3
  1. #1
    Join Date
    Mar 2009
    Posts
    1

    Unanswered: student registration database design...

    dear all,
    this is my first post to this site and m looking forward to solution of my problem thru this site.
    my problem is very common but i don find it simple as m quite new to this area.
    i am creating a site for student registration in asp.net in that i want to design the database..so far i cd only think of the following tables. please help me with that so that in future i will not face any problem because of bad databse design...
    student table:
    StudentID, CourseID, name ,(other personal info
    course table:
    CourseID, courseName
    CourseDetail(one for each course ID)
    Sem,Sub1....Sub10(as the number of subjects may vary from course to course)
    college table
    collegeid,courseID,(college details)

    is this pattern alright?
    my mail query iswhilke connecting the coursedetail table to course table.
    for every course i need one seperate table as one course has different sujects in different semesters.
    please lemme know any other way out also if easier or better than this

    thanx in advance...
    looking forward to get my query solved.
    -Annu

  2. #2
    Join Date
    Jan 2009
    Location
    United Kingdom
    Posts
    77
    I think you may need to add one more table , something like "student_course" , this would have at least 2 columns "StudentID" and CourseID , rather than having CourseID in the Student Tabble. This is on the assumption a student may be on more than 1 course

  3. #3
    Join Date
    Nov 2004
    Posts
    1,427
    Provided Answers: 4

    Thumbs up

    STUDENT
    StudentID, Name, (other info)
    COURSE
    CourseID, Name, (other info)
    STUDENT_COURSE (all courses a student takes)
    StudentID, CourseID
    COURSESUBJECT
    SubjectId, CourseID, Sem, Sub, (other info)
    COLLEGE
    collegeid, (other info)
    COLLEGE_COURSE (all courses in a college)
    CollegeID, CourseID
    With kind regards . . . . . SQL Server 2000/2005/2012
    Wim

    Grabel's Law: 2 is not equal to 3 -- not even for very large values of 2.
    Pat Phelan's Law: 2 very definitely CAN equal 3 -- in at least two programming languages

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •