|
A couple of observations:
As has been stated, there is no practical reason you cannot (and sometimes there might be a good reason) put several sites on a single database. 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. Nor is all maintenance easier: if you discontinue or change the software for a site using its own database, you only have to delete or empty the one database, not go through a potentially huge database, trying to track the relevant tables.
Secondly, although if you are careful - again as stated - you can avoid problems, there is the potential for sites on the same IP and even more in the case of sub-domains, to end up being treated by the SE's as a single site.
Unless you have a host who is mean with his IP's or very small-time, it shouldn't cost more than a dollar a month (if anything) for each IP address in a different group C. That also isn't a guarantee for no problems, but it's a (frequently) cheap and easy way to make problems a lot less likely.
|