[solved]For multiple sites on the same server, should I...? <mysql question

Help with getting the CMS CORE package up and running. This does not include 3rd party modules, PHP scripts, anything downloaded via module manager or from any external source.
Locked
greenftechn
Forum Members
Forum Members
Posts: 36
Joined: Wed Sep 26, 2007 10:53 pm

[solved]For multiple sites on the same server, should I...? <mysql question

Post by greenftechn »

I want the flexibility of being able to move sites without losing data from one server to another. When I create multiple sites on the same server, should I simply use a different table prefix for different sites, or should I create entirely separate databases? I'm not a mysql expert, but my initial hunch is that it makes little difference. My thinking is that exporting an entire database, or just those belonging to a particular site, identified by the prefix, are roughly equivalent. I could be wrong, and would like to know before I do a dozen more sites and somebodies needs moved. Portability may not be the only issue here. Performance might enter in as well. Thanks in advance!
Last edited by greenftechn on Fri May 14, 2010 4:36 pm, edited 1 time in total.
Peciura

Re: For multiple sites on the same server, should I...? <mysql question>

Post by Peciura »

It would work either way.
If you are using phpMyAdmin make sure file is imported within php max_execution_time limit, or you can split big files into pieces.
I would keep  separate DBs for each site, because it takes just seconds to reimport sql files. And of course big/busy  sites should be on separate DBs.
greenftechn
Forum Members
Forum Members
Posts: 36
Joined: Wed Sep 26, 2007 10:53 pm

[solved] Re: For multiple sites on the same server, should I...? <mysql question

Post by greenftechn »

Thanks. I think separate DBs are the best approach for modularity. Will do that from now on.
Locked

Return to “[locked] Installation, Setup and Upgrade”