[thelist] Single or multiple MySql databases.

[Duncan Hill]

On Wed, 22 Oct 2008 16:07:34 +0100, Matt Warden <mwarden at gmail.com> wrote:

> On Wed, Oct 22, 2008 at 4:17 AM, Duncan Hill <dunkaz at gmail.com> wrote:
>> I am building a new site that makes use of normal static html pages  
>> plus 2
>> separate Wordpress blogs, aMember membership management, and PHPlist for
>> newsletter posting etc.
>> Apart from the static pages, the other apps all run from MySql databases
>> ... what are the pros and cons of using either a single database that  
>> they
>> all access, or individual databases for each app.
>>
>> I don't need to run any special queries on the databases (that I can
>> foresee).
>>
>> Many thanks for any words of wisdom.
>
> I assume you mean databases on the same server rather than separate
> database servers. If you put all the tables in the same database, it
> is somewhat more difficult to make sure the user for wordpress does
> not have access to aMember tables, etc. You would also need to make
> sure that table names do not conflict across applications. I don't see
> any benefit to putting all the tables in the same database in MySQL.
>
Thanks Matt,

Yes the databases will all be on one server, I'm reasonably happy that  
users won't be able to access, the Wordpress is view only without any post  
or comment rights for general users. Each of the apps applies its own  
prefix to the tables that relate to it, and aMember and PHPlist both  
appear to integrate with Wordpress by using more or less common fields.  
That is what made me consider a single database in the first place.
I thought a single database may make for easier backups and a simpler  
configuration.

I'll certainly check for crossover access before I commit to one or  
several.

Duncan