Thank you for writing back JayBee,
my design is getting bigger and bigger but the solution i m thinking to my question is below. i dont know if this is the best solution but seems like one to me.
and answers to your questions are also below.
thanks again
JayBee wrote:
Hi Shane,
Before one can answer your questions, you should first show the model you have designed.
You probably have School, Tutor, Pupil, Class, etc. in your logical datamodel.
Jan
yes there is school, people (which has student, teacher,parent as subtypes), room, course, class etc in the model. the solution i m thinking is using a third table for the main tables like people table or course table such as PeopleAcademicYear which will keep the PeopleID and AcademicYearID as primary keys. if same person is enrolled for the next school year there will be one more row created for him in PeopleAcademicYear table. Same for Courses or Attendance or Assignments etc.
JayBee wrote:
It would also be nice to know which database (SQLServer, SQLServer Express, Oracle, DB2, ..) you are planning to use and some info on the number of schools (20?), tutors, pupils, etc.
Jan
Will be using sqlserver express and will switch to sqlserver depending on the size and needs in the future. There will be 20 schools at the beginning which may go up to 50 in the next 5 years. Total staff will be around 600 at the beginning and may go up to 1500 in the next 5 years. Total number of students will be around 5000 and may go up to 15000 in the next 5 years. These numbers are not big numbers but again the attendance records by itselt will be close to million rows at the end of the first yeat with 20 schools and 5000 students. This may go up to 3-5 million rows just for the attendance in the next 5 years.
Again i dont know if my design is a good design and dont want to make the mistake of starting with a wrong design and getting stuck in 2 years.
Thanks again
-shane