Posts in a different database?
 

I've been trying to think of a way to separate the posts into a different MySQL database. For some reason, our host has a cap of about 200 megs on database size, and ours is continually approaching that barrier (I've taken to clearing out our search indexes and reindexing about 25,000 posts every week or so to keep us under the cap).

So, with posts representing about 110 megs of my database size right now, I'm curious as to whether there's a way to have posts stored in a second database (because the host doesn't limit the number of databases, just the size of each individual one) with 3.5? I know it's something I'd have to hack, but if someone could point me in the right direction on where to start this, I'd be able to write it myself and release it here for anyone who's in a similiar situation.

Thanks for any help you guys can give me. I'm truly stumped on where to even begin this.

Get a new host. Who is your host?

Also, if you haven't done so already, move your attachments, avatars, and profile pics to the file system instead of stored in the DB.

Site5 is my host. Other than that database thing, we haven't had any problems with them whatsoever in the month and a half we've been there. Honestly, they're the first host that hasn't complained about vB, so switching isn't really an option.

Avatars, profile pics, and attachments are already out of the DB. Not really sure what else we can store externally aside from the posts (all 140,000+ of them...).

I've never had a host complain about vB...

I've used Site5 before but left due to stupid policies such as that one as well as others that came up.

It would be a severe hacking of the files to find every reference to the post table. Simple answer is move host.