Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Pages: 1
One database or many?
Say I have a client who has a bunch of related websites. They’re all distinct in terms of what they present to the public, but they share a common data source Txp instance.
Currently I have three separate databases; one for each site. Since I don’t have infinite databases on my hosting plan, I’m considering moving these three DBs to a single database, with three different table prefixes.
Presumably, access credentials would be the same for all three sites. My question is: are there performance implications in doing this? For example, if one site is executing a transaction to update a table, do the other instances have to wait, or can they all access the database concurrently via the same user to fetch/update their own prefixed tables?
Are there any other downsides? Security?
The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.
Hire Txp Builders – finely-crafted code, design and Txp
Offline
Re: One database or many?
I have been running 2 websites on the same database without any issues for years now.
I guess that security might be an issue if one site is hacked.
On the positive side, your client will be able to repair any tables with rss_admin_db_manager from any site, or just have only one instance for phpMyAdmin.
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Pages: 1