I would like to design a Attendance DB for following specs
*) There are 4 branches
*) Each branch has 60 Students

My first design

BRANCH
+ BranchID
+ BranchName

STUDENT
+ StudentID
+ StudentName

CLASSATTENDANCE
+ ClassID
+ Date
+ StudentID
+ Present
+ LeaveApplied

Here's my problems

I)
We have at least 4 Branches. There are 60 students in each branch.
So 60 * 4 = 240 records(tuples) in the CLASSATTENDANCE table per day. The records spanning even 6 months would be very large. I think the table would be too large to manage.
-----
I would like to know if there is more convenient way.

II)
CLASSATTENDANCE table solely depends on 'Date' attribute to identify the chronological order. Is there a better way, like categorizing by months.

I think creating a table for each month would solve it, like a table 'CLASSATTENDANCE+[MONTHNAME]'
------
Is that a good solution or is there any better one?

I) 240 rows per day is not "very large" or "too large to manage" unless you ran this application for several thousand years

II) that's a horrible solution

I) OK. I Agree.

II) Then what would be a better solution man?!

what you have now

by the way, what's a branch? and how come there isn't a class table?

OK. I was just worrying cause this is my first time with Database.

Branch is same as class, but also tells which class one is taking like Information Technology branch.

Thank You for your help.

present and leaveapplied for in the same table doesn't feel right
they have the feel of mutually opposed data
ie either they are present or not

you may be better to have say an attendance code / type
which then subclassifies the attendance record
to, say
present
absent
absent, medical appointment
absent with prior knowledge
....and so on

Do you want me to move 'leaveapplied' field to another table and use according to the value in the 'present' field?

If that is the case, how should I do it?

No I want you to do your own assignment, go through the design process, work out what you need, understand why you went down some blind allys and learn from the process. is just as valuable doing something wrong and learning form that as doing something right. often if you get others to do your homework you don't actually learn from the process. equally what contributors here tend to do is look at a data model from a real world perspective, from their experience and that may not be appropriate for validation of coursework

understand about relational table design, eliminating redundancies, duplications and so on.

Ok man. Will let you know if anything comes up.