Splitting posts/topics to an extra db-table

[Peetra]

Well, after a fatal db-crash a few weeks ago ppl on a forum I admin on have been thinking of splitting the topis into one(or more) table, we could call them prefix_posts_old and prefix_topics_old. Someone also mentioned that they migfht should be searchable.

Someone that done anything like this and should it really be necessary? Not even 500 000 posts on the forum I mean.

Peetra.

[RMcGirr83]

For what purpose...I mean why do that?

[tumba25]

Totally unnecessary. I assume that you would still want them to be accessible through the forum. I'm trying hard to find any gain with doing that, but with no success. Depending on what file system you have, you can have a table size of at least 2TB and that is a lot more than 500k posts.

[Peetra]

For what purpose...I mean why do that?

The posts table crashed and it wouldn't allow the fixer to fix it, he was working on it an whole afternoon and then we had the put in a backup. SO that was the reason ppl began to think it might would be a good idea to have a lighter

And then there is a need to separate old post/forums with data that are irrelevant today/aka archived. So if we put 70% of all posts in a static searchable table, maybe all locked or something like that, the normal posts table should be much lighter then.

[tumba25]

I'm sure the table crash or not being able to fix it has nothing to do with the table size.

You would need to do some heavy modifying to get that to work well with your forum. The disadvantages would probably be much greater than the advantages.

I think you seem to try to fix the wrong error, you should probably look at PEBKAC.

[Peetra]

I am just the messenger here but I am sure the community slaps tumba25 for PEBKAC.