Re: One big database or little separate ones?

On Sat, 10 Jan 2004, Dennis Veatch wrote:

> In creating a database I am trying to determine which method is the better way
> to go. No, I do not know what "better way" means, novice is the key, hence
> this post.
>
> The basic question is, what point(s) are used to determine there are enough
> tables and another database should be created. Hmm, well let me say it this
> way.
>
> Here are briefly (for the most part) the things I want in a database;
>
> 1. customers - the usual stuff, names, addresses, etc.
> 2. well logs - depth of water wells, location (latitude/longitude as well as
> the normal address), layers drilled through, etc.
> 3. excavator work - hourly rate, length of dig, etc.
> 3. plumbing - items used on project, part cost, etc
> 4. septic work - installation of septic tanks, address, cost, etc
> 5. water softeners - customer name, is it a rental or not
> 6. supplies/parts - inventory type stuff.
>
> The basic decision here is, do I put all this into one database with a bunch
> of table? Or would it make more sense to separate it out? If there are
> separate databases will it prevent linking tables between the two?

Can a customer move, and request a new well be dug? Can someone
move into a place where you put in a well before, and ask you to
do something to the existing well? Does a well ever cave in, or
need new excavating work? Do you ever get called in to change
plumbing on a well? Same sort of questions vis a vis septic
systems and water softeners.

If these sort of questions need a yes answer, then you might want
to consider having other tables.

Gord