Different Modules Decision

Hi all, I need advice. If we are developing a database, what are the triggering points to have different modules for a database? For example, I'm doing a database for a company's activities. This company has different activities, is it best to segregate and group each activity into each module in the database instead of having them in one whole database? Please let me know your views and consideration to have different modules for a database, thank you.

Sandra

I'm not sure what you mean by modules -- tables?

Try a quick google on database normalization -- I think that's what you're asking about.

or tablespaces???

I think he's referring to tables.
The best way I always look at it is... if there's redundant data, and I make a spelling mistake on one of the records [or many of them, all different mistakes], how badly will that fudge all my data... and how hard will it be to fix it... Often it's best to look at breaking that field out into it's own table...

Definately read up on normalization though, as I've only given a simple example.