Hi,

just a question to get your views on this - is there any upside/downside of installing gossamer mail, linksSQL, wwwthreads... etc etc etc into one database but still using their own tables..

vs

installing them each with their own unique database.

It seems it would make each of them more accessible to the other if they were all in the same one. Are there any technical issues with putting them all into one mixing pot?

Cheers,
Regan.

There are advantages and disadvantages to using separate databases....

ADVANTAGES:

1) Keeps tables organized. (Less time to maintain them.)

2) In terms of "connecting", it is better to separate data into multiple databases since your users will not be connecting to the same database for all your applications.

DISADVANTAGES:

1) More complicated to code scripts to connect to one user table that may be in another database.

2) More complicated to install plugins that are TABLE/DATABASE dependent, since you would have to hack them to work between multiple databases.

Regards,

Eliot Lee

One other problem, is the more tables in each database, the more files. Each table is a file, and each table has 2 associated files. The more tables in each database, the more files in each directory, and the more of a performance hit you'll take on the OS. 100 tables, is 300 files.



PUGDOG® Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum

Hi,

If you are under mod_perl and using persistent connections, it will be much better to have everything in the same database as then you only need one connection per apache. If each were in a separate database then you would need 3 connections per apache.

The main advantadge to having them separated is security. If each application has it's own database with own username/password, then if there is a hole in one, it won't/can't affect the other applications.

Cheers,

Alex

--
Gossamer Threads Inc.