I have started to design a database for a company which I work for. I am curious how the professionals would design such a database and what advice you might carry.
Information about the database:
The database is a reflection of activities which are all completely different. Basically there are around seven activities which each carry their own set of information. This means that it is hard to standardize the database and simply make a table called 'activities' which suffices for the entire database.
I was thinking of using a seperate table for each activity and link those to a couple of tables with basic information like the geographic information and/or the employee who was/is involved.
If this is the case then I at least know that I am on the right path and if I am not right, then I have learned something important!
If the information provided is not complete, then feel free to ask for more!