For monitoring recruitment actions per applicant I need to store about 50
actions per applicant. The activity table would look like:

ApplicantID*
ActivityID*
DateStart
DateEnd

My concerns a
1. The table would have an enormous amout of records if I had let's say
30,000 applicants.
2. When an new applicant would be added I would have to automatically add
all the 50 action records, otherwise the user would have to pick them
manually. Also some jobs require other applicant actions than others.

A not normalized table would seem easier but would require a table design
change every time there was a new type of action, which is also not
desirable.

How would you deal with such a situation?

Thanks, Lars