two more things: if you have a need to migrate one of the sites to it's own install at some point (because of high traffic for example) it would be a bigger job to migrate the database.
It's been a while since I did significant database management (beyond normal setting up of databases, tables users etc) but if I remember correctly you can set things such as concurrent connections per databsae not just per user - if your host is charging per database it's likely they have that set up so doing this could have performance limitations (eg. high traffic on one site resulting in decreased performance on the other sites or even make them inaccessible)
.s
Ivan Sergio Borgonovo wrote:
On Thu, 18 Oct 2007 14:38:34 +0200 Daniel Carrera daniel.carrera@zmsl.com wrote:
Hello,
In a multi-site, where all the sites share the same installation, is it also a good idea to have them all share the same database but using a different prefix? Or is there a reason why this would be a bad idea? I would prefer to have fewer databases since my webhost
The first thing that comes to my mind is separate backup. The second thing is separate access/write permissions.