Re: One database vs. hundreds?

am Tue, dem 28.08.2007, um 8:08:36 -0400 mailte Kynn Jones folgendes:
> I'm hoping to get some advice on a design question I'm grappling with.
> I have a database now that in many respects may be regarded as an
> collection of a few hundred much smaller "parallel databases", all
> having the same schema. What I mean by this is that, as far as the
> intended use of this particular system there are no meaningful queries
> whose results would include information from more than one of these
> parallel component databases. Furthermore, one could delete all the

Maybe different schemas, one schema for every "parallel databases", can
help you. And different rights for the users.

Why one database with many schemas?

I suppose, you have objects to share with all users, for instance:
- programming languages
- stored procedures
- maybe shared data

Andreas
--
Andreas Kretschmer
Kontakt: Heynitz: 035242/47150, D1: 0160/7141639 (mehr: -> Header)
GnuPG-ID: 0x3FFF606C, privat 0x7F4584DA http://wwwkeys.de.pgp.net