Quote:
|
The only thing to bear in mind is that databases do sometimes crash and one database per site means only one site going down on such occasions.
|
This is certainly good advice. But if your blogs are all on the same machine, then there will be one piece of software running all the databases. If it crashes, all the databases will crash. You just gotta hope that doesn't happen.
I'm an advocate of using different databases just so you can keep them separated for ease of maintenance (like has been stated before) and also so that if a hacker manages to compromise one db (i.e. they manage to acquire the password or somesuch) then your other blogs are protected.
And I'll reiterate Jayeff's comments about SEs. They
will notice that all the blogs have the same IP and they may decide to treat them as the same site. If you take twn's advice and never link the blogs to each other, however, you may avioid this.
Jayeff is also quite right to reccomend you get a different IP for each domain if you can do so without too much cost (that could be difficult -- your host has to be able to provide justification to ICANN for the extra IPs. But then I've never tried it myself...) If you do, you'll still want to keep the interlinking to a minimum, tho. Even with separate IPs, the SEs will still be able to tell that the different blogs are on the same hosting service if not the same machine. So if the blogs all seem closely affiliated with each other then the SEs may decide to treat them as if they are owned by the same person.