I have a database with students. I import a bunch of fields and then have a bunch of calc and summary fields based on that import, so there are a total of 282 fields. Then I have a related table called "Student_Additional" which has another 138 related fields where we add our own internal information about students, and calcs on those. Then I have a third table which is for intaking new students which has another 64 fields. All told that's 484 student-related fields.
One thing I'm finding is I end up doing a lot of backflips around wanting to do a calculation or a SQL call which (for example) is based on the student program (which is in the main Students table) and who their advisor is (which is in Student Additional)... and they're just more complicated.
I'm debating the pros and cons of spending a little time merging those two and getting rid of the "additional" table... but that means I'd have over 400 fields in that database, which makes it a little harder to work with.
Are there any technical reasons why I shouldn't merge them? Am I going to have speed problems (or speed improvements) if these 400+ fields are in the same table as opposed to split among two different tables?