MySQL 4.0.12 = forum problems...

[sagewebhosting]

For the last week or so I have had many Database errors, usually something different each time.

I've then took sometime and looked into it over at vBulletin.com thinking it was a problem with the software, then I found THIS (http://www.vbulletin.com/forum/showthread.php?threadid=69803) thread.

Seems as if there have been a great deal of people having problems with the new version of MySQL, myself being one of them. So my question is this, does alphaomegahosting have any servers that is NOT currently running 4.0.12 of MySQL. Maybe the next version down, as that seems to be what a lot of people over at vBulletin.com is doing.

If we do have any servers that is running the next version down of MySQL then I'd like to be moved to that server, or if possible would you Danny do whats suggested in the link above since it requires root access to the server.


Thanks,

-Michael

[admin]

This is quite interesting. However, I am inclined to believe this may be more related to the server move than the version of mysql. Here are a couple reasons why I think so.

The server has been running 4.0.12 for about a month.
There are ALOT of forums running on our 15 or so cpanel servers and this is the first I have heard of corruption.

If you want to put in a ticket for more assistance, I will take a look at your database specifically and see if I can attempt to repair it. I think it is more likely that when your account was moved to the new server, the database may have been being updated and resulted in corruption.

[Rodzilla]

I haven't been having problems with vB, but two of my scripts went into the land of bugville a few months ago when PHP (and MySQL?) were updated...maybe this is related...

Edit: Nevermind, this is table corruption, my problems were completely different. Yea, following the server move some of our tables were corrupted. I ran the repair script on the whole database and it fixed them as well as optimized them. Ten minutes later they became corrupt again, but after running the script they've been fine ever since.