Re: when to use multiple databases

Well I guess in theory the entire world only needs a single database.

Of course in practice this isn't done, but I think I'm right in saying this is for physical reasons. Namely the problems of finding a DBMS to run it on. Also the problems of the single namespace for tables. You'd end up encoding a kind of hierarchical naming convention in the table names: CountyA_CompanyB_DeptC_Sales or whatever. Not to mention the political problem of who controls access etc.

It does raise the question: does the "database" structure serve any theoretical purpose? Or could we just have a "Universe" that contains tables, etc.?

Going the other way, might it be useful to have databases grouped together? But then you're going down the road of hierarchies which aren't nice for first-order logic.

> The DBMS I'm using (Postgresql) doesn't allow cross-database queries,

Speaking more practically now, I think this is your deciding factor: use a single database.

> When is it wise/practical to use multiple databases if all those
> databases have the same schema?

Speaking theoretically I'd say never. But there may be physical reasons for it.

Paul. Received on Sun Apr 04 2004 - 16:15:14 CEST