Database corruption keeps occuring

**fccsonline** · Thu 21 Jul '11, 4:33am

To add, when optimizing tables:

Results
Table	Action	Message
access	Check	Status: OK
access	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
access	Optimize	Status: OK
action	Check	Status: OK
action	Optimize	Status: OK
ad	Check	Status: OK
ad	Optimize	Status: OK
adcriteria	Check	Status: OK
adcriteria	Optimize	Status: OK
adminhelp	Check	Status: OK
adminhelp	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
adminhelp	Optimize	Status: OK
administrator	Check	Status: OK
administrator	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
administrator	Optimize	Status: OK
adminlog	Check	Status: OK
adminlog	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
adminlog	Optimize	Status: OK
adminmessage	Check	Status: OK
adminmessage	Optimize	Status: OK
adminutil	Check	Status: OK
adminutil	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
adminutil	Optimize	Status: OK
adv_modules	Check	Status: OK
adv_modules	Optimize	Status: OK
adv_pages	Check	Status: OK
adv_pages	Optimize	Status: OK
adv_setting	Check	Status: OK
adv_setting	Optimize	Status: OK
adv_settinggroup	Check	Status: OK
adv_settinggroup	Optimize	Status: OK
album	Check	Status: OK
album	Optimize	Status: OK
albumupdate	Check	Status: OK
albumupdate	Optimize	Status: OK
announcement	Check	Status: OK
announcement	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
announcement	Optimize	Status: OK
announcementread	Check	Status: OK
announcementread	Optimize	Status: OK
apiclient	Check	Status: OK
apiclient	Optimize	Status: OK
apilog	Check	Status: OK
apilog	Optimize	Status: OK
attachment	Check	Status: OK
attachment	Optimize	Status: OK
attachmentcategory	Check	Status: OK
attachmentcategory	Optimize	Status: OK
attachmentcategoryuser	Check	Status: OK
attachmentcategoryuser	Optimize	Status: OK
attachmentpermission	Check	Status: OK
attachmentpermission	Optimize	Status: OK
attachmenttype	Check	Status: OK
attachmenttype	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
attachmenttype	Optimize	Status: OK
attachmentviews	Check	Status: OK
attachmentviews	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
attachmentviews	Optimize	Status: OK
autosave	Check	Status: OK
autosave	Optimize	Status: OK
avatar	Check	Status: OK
avatar	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
avatar	Optimize	Status: OK
bbcode	Check	Status: OK
bbcode	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
bbcode	Optimize	Status: OK
bbcode_video	Check	Status: OK
bbcode_video	Optimize	Status: OK
block	Check	Status: OK
block	Optimize	Status: OK
blockconfig	Check	Status: OK
blockconfig	Optimize	Status: OK
blocktype	Check	Status: OK
blocktype	Optimize	Status: OK
blog	Check	Status: OK
blog	Optimize	Status: OK
blog_attachmentlegacy	Check	Status: OK
blog_attachmentlegacy	Optimize	Status: OK
blog_category	Check	Status: OK
blog_category	Optimize	Status: OK
blog_categorypermission	Check	Status: OK
blog_categorypermission	Optimize	Status: OK
blog_categoryuser	Check	Status: OK
blog_categoryuser	Optimize	Status: OK
blog_custom_block	Check	Status: OK
blog_custom_block	Optimize	Status: OK
blog_custom_block_parsed	Check	Status: OK
blog_custom_block_parsed	Optimize	Status: OK
blog_deletionlog	Check	Status: OK
blog_deletionlog	Optimize	Status: OK
blog_editlog	Check	Status: OK
blog_editlog	Optimize	Status: OK
blog_featured	Check	Status: OK
blog_featured	Optimize	Status: OK
blog_groupmembership	Check	Status: OK
blog_groupmembership	Optimize	Status: OK
blog_grouppermission	Check	Status: OK
blog_grouppermission	Optimize	Status: OK
blog_hash	Check	Status: OK
blog_hash	Optimize	Status: OK
blog_moderation	Check	Status: OK
blog_moderation	Optimize	Status: OK
blog_moderator	Check	Status: OK
blog_moderator	Optimize	Status: OK
blog_pinghistory	Check	Status: OK
blog_pinghistory	Optimize	Status: OK
blog_rate	Check	Status: OK
blog_rate	Optimize	Status: OK
blog_read	Check	Status: OK
blog_read	Optimize	Status: OK
blog_relationship	Check	Status: OK
blog_relationship	Optimize	Status: OK
blog_search	Check	Status: OK
blog_search	Optimize	Status: OK
blog_searchresult	Check	Status: OK
blog_searchresult	Optimize	Status: OK
blog_sitemapconf	Check	Status: OK
blog_sitemapconf	Optimize	Status: OK
blog_subscribeentry	Check	Status: OK
blog_subscribeentry	Optimize	Status: OK
blog_subscribeuser	Check	Status: OK
blog_subscribeuser	Optimize	Status: OK
blog_summarystats	Check	Status: OK
blog_summarystats	Optimize	Status: OK
blog_tachyentry	Check	Status: OK
blog_tachyentry	Optimize	Status: OK
blog_text	Check	Status: OK
blog_text	Optimize	Status: OK
blog_textparsed	Check	Status: OK
blog_textparsed	Optimize	Status: OK
blog_trackback	Check	Status: OK
blog_trackback	Optimize	Status: OK
blog_trackbacklog	Check	Status: OK
blog_trackbacklog	Optimize	Status: OK
blog_user	Check	Status: OK
blog_user	Optimize	Status: OK
blog_usercss	Check	Status: OK
blog_usercss	Optimize	Status: OK
blog_usercsscache	Check	Status: OK
blog_usercsscache	Optimize	Status: OK
blog_userread	Check	Status: OK
blog_userread	Optimize	Status: OK
blog_userstats	Check	Status: OK
blog_userstats	Optimize	Status: OK
blog_views	Check	Status: OK
blog_views	Optimize	Status: OK
blog_visitor	Check	Status: OK
blog_visitor	Optimize	Status: OK
bookmarksite	Check	Status: OK
bookmarksite	Optimize	Status: OK
cache	Check	Status: OK
cache	Optimize	Status: OK
cacheevent	Check	Status: OK
cacheevent	Optimize	Status: OK
calendar	Check	Status: OK
calendar	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
calendar	Optimize	Status: OK
calendarcustomfield	Check	Status: OK
calendarcustomfield	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
calendarcustomfield	Optimize	Status: OK
calendarmoderator	Check	Status: OK
calendarmoderator	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
calendarmoderator	Optimize	Status: OK
calendarpermission	Check	Status: OK
calendarpermission	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
calendarpermission	Optimize	Status: OK
cms_article	Check	Status: OK
cms_article	Optimize	Status: OK
cms_category	Check	Status: OK
cms_category	Optimize	Status: OK
cms_grid	Check	Status: OK
cms_grid	Optimize	Status: OK
cms_layout	Check	Status: OK
cms_layout	Optimize	Status: OK
cms_layoutwidget	Check	Status: OK
cms_layoutwidget	Optimize	Status: OK
cms_navigation	Check	Status: OK
cms_navigation	Optimize	Status: OK
cms_node	Check	Status: OK
cms_node	Optimize	Status: OK
cms_nodecategory	Check	Status: OK
cms_nodecategory	Optimize	Status: OK
cms_nodeconfig	Check	Status: OK
cms_nodeconfig	Optimize	Status: OK
cms_nodeinfo	Check	Status: OK
cms_nodeinfo	Optimize	Status: OK
cms_permissions	Check	Status: OK
cms_permissions	Optimize	Status: OK
cms_rate	Check	Status: OK
cms_rate	Optimize	Status: OK
cms_sectionorder	Check	Status: OK
cms_sectionorder	Optimize	Status: OK
cms_widget	Check	Status: OK
cms_widget	Optimize	Status: OK
cms_widgetconfig	Check	Status: OK
cms_widgetconfig	Optimize	Status: OK
cms_widgettype	Check	Status: OK
cms_widgettype	Optimize	Status: OK
contentpriority	Check	Status: OK
contentpriority	Optimize	Status: OK
contenttype	Check	Status: OK
contenttype	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
contenttype	Optimize	Status: OK
cron	Check	Status: OK
cron	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
cron	Optimize	Status: OK
cronlog	Check	Status: OK
cronlog	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
cronlog	Optimize	Status: OK
customavatar	Check	Status: OK
customavatar	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
customavatar	Optimize	Status: OK
customprofile	Check	Status: OK
customprofile	Optimize	Status: OK
customprofilepic	Check	Status: OK
customprofilepic	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
customprofilepic	Optimize	Status: OK
datastore	Check	Status: OK
datastore	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
datastore	Optimize	Status: OK
dbquery	Check	Status: OK
dbquery	Optimize	Status: OK
deletionlog	Check	Status: OK
deletionlog	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
deletionlog	Optimize	Status: OK
discussion	Check	Status: OK
discussion	Optimize	Status: OK
discussionread	Check	Status: OK
discussionread	Optimize	Status: OK
editlog	Check	Status: OK
editlog	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
editlog	Optimize	Status: OK
event	Check	Status: OK
event	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
event	Optimize	Status: OK
externalcache	Check	Status: OK
externalcache	Optimize	Status: OK
faq	Check	Status: OK
faq	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
faq	Optimize	Status: OK
filedata	Check	Status: OK
filedata	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
filedata	Optimize	Status: OK
forum	Check	Status: OK
forum	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
forum	Optimize	Status: OK
forumpermission	Check	Status: OK
forumpermission	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
forumpermission	Optimize	Status: OK
forumprefixset	Check	Status: OK
forumprefixset	Optimize	Status: OK
forumread	Check	Status: OK
forumread	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
forumread	Optimize	Status: OK
groupmessage	Check	Status: OK
groupmessage	Optimize	Status: OK
groupmessage_hash	Check	Status: OK
groupmessage_hash	Optimize	Status: OK
groupread	Check	Status: OK
groupread	Optimize	Status: OK
holiday	Check	Status: OK
holiday	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
holiday	Optimize	Status: OK
humanverify	Check	Status: OK
humanverify	Optimize	Status: OK
hvanswer	Check	Status: OK
hvanswer	Optimize	Status: OK
hvquestion	Check	Status: OK
hvquestion	Optimize	Status: OK
icon	Check	Status: OK
icon	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
icon	Optimize	Status: OK
imagecategory	Check	Status: OK
imagecategory	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
imagecategory	Optimize	Status: OK
imagecategorypermission	Check	Status: OK
imagecategorypermission	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
imagecategorypermission	Optimize	Status: OK
indexqueue	Check	Status: OK
indexqueue	Optimize	Status: OK
infraction	Check	Status: OK
infraction	Optimize	Status: OK
infractionban	Check	Status: OK
infractionban	Optimize	Status: OK
infractiongroup	Check	Status: OK
infractiongroup	Optimize	Status: OK
infractionlevel	Check	Status: OK
infractionlevel	Optimize	Status: OK
language	Check	Status: OK
language	Optimize	Status: OK
mailqueue	Check	Status: OK
mailqueue	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
mailqueue	Optimize	Status: OK
moderation	Check	Status: OK
moderation	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
moderation	Optimize	Status: OK
moderator	Check	Status: OK
moderator	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
moderator	Optimize	Status: OK
moderatorlog	Check	Status: OK
moderatorlog	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
moderatorlog	Optimize	Status: OK
notice	Check	Status: OK
notice	Optimize	Status: OK
noticecriteria	Check	Status: OK
noticecriteria	Optimize	Status: OK
noticedismissed	Check	Status: OK
noticedismissed	Optimize	Status: OK
package	Check	Status: OK
package	Optimize	Status: OK
passwordhistory	Check	Status: OK
passwordhistory	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
passwordhistory	Optimize	Status: OK
paymentapi	Check	Status: OK
paymentapi	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
paymentapi	Optimize	Status: OK
paymentinfo	Check	Status: OK
paymentinfo	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
paymentinfo	Optimize	Status: OK
paymenttransaction	Check	Status: OK
paymenttransaction	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
paymenttransaction	Optimize	Status: OK
phrase	Check	Status: OK
phrase	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
phrase	Optimize	Status: OK
phrasetype	Check	Status: OK
phrasetype	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
phrasetype	Optimize	Status: OK
picturecomment	Check	Status: OK
picturecomment	Optimize	Status: OK
picturecomment_hash	Check	Status: OK
picturecomment_hash	Optimize	Status: OK
picturelegacy	Check	Status: OK
picturelegacy	Optimize	Status: OK
plugin	Check	Status: OK
plugin	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
plugin	Optimize	Status: OK
pm	Check	Status: OK
pm	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
pm	Optimize	Status: OK
pmreceipt	Check	Status: OK
pmreceipt	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
pmreceipt	Optimize	Status: OK
pmtext	Check	Status: OK
pmtext	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
pmtext	Optimize	Status: OK
pmthrottle	Check	Status: OK
pmthrottle	Optimize	Status: OK
podcast	Check	Status: OK
podcast	Optimize	Status: OK
podcastitem	Check	Status: OK
podcastitem	Optimize	Status: OK
poll	Check	Status: OK
poll	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
poll	Optimize	Status: OK
pollvote	Check	Status: OK
pollvote	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
pollvote	Optimize	Status: OK
post	Check	Status: OK
post	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
post	Optimize	Status: OK
postedithistory	Check	Status: OK
postedithistory	Optimize	Status: OK
posthash	Check	Status: OK
posthash	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
posthash	Optimize	Status: OK
postindex	Check	Status: OK
postindex	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
postindex	Optimize	Status: OK
postlog	Check	Status: OK
postlog	Optimize	Status: OK
postparsed	Check	Status: OK
postparsed	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
postparsed	Optimize	Status: OK
prefix	Check	Status: OK
prefix	Optimize	Status: OK
prefixpermission	Check	Status: OK
prefixpermission	Optimize	Status: OK
prefixset	Check	Status: OK
prefixset	Optimize	Status: OK
product	Check	Status: OK
product	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
product	Optimize	Status: OK
productcode	Check	Status: OK
productcode	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
productcode	Optimize	Status: OK
productdependency	Check	Status: OK
productdependency	Optimize	Status: OK
profileblockprivacy	Check	Status: OK
profileblockprivacy	Optimize	Status: OK
profilefield	Check	Status: OK
profilefield	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
profilefield	Optimize	Status: OK
profilefieldcategory	Check	Status: OK
profilefieldcategory	Optimize	Status: OK
profilevisitor	Check	Status: OK
profilevisitor	Optimize	Status: OK
ranks	Check	Status: OK
ranks	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
ranks	Optimize	Status: OK
reminder	Check	Status: OK
reminder	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
reminder	Optimize	Status: OK
reputation	Check	Status: OK
reputation	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
reputation	Optimize	Status: OK
reputationlevel	Check	Status: OK
reputationlevel	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
reputationlevel	Optimize	Status: OK
route	Check	Status: OK
route	Optimize	Status: OK
rssfeed	Check	Status: OK
rssfeed	Optimize	Status: OK
rsslog	Check	Status: OK
rsslog	Optimize	Status: OK
searchcore	Check	Status: OK
searchcore	Optimize	Note: Table does not support optimize, doing recreate + analyze instead
searchcore	Optimize	Status: OK
searchcore_text	Check	Status: OK
searchcore_text	Optimize	Error: 137 when fixing table
searchcore_text	Optimize	Status: OK

**fccsonline** · Thu 21 Jul '11, 4:34am

And then I immediately received a database error:
Database error in vBulletin 4.1.4:
Invalid SQL:
CHECK TABLE `searchgroup`;
MySQL Error : MySQL server has gone away
Error Number : 2006
Request Date : Thursday, July 21st 2011 @ 07:25:18 AM
Error Date : Thursday, July 21st 2011 @ 07:30:02 AM
Script : http://www.xxxxxx/forum/admincp/repair.php?do=dorepair
Referrer : http://www.xxxxxx/forum/admincp/repair.php?do=list
IP Address : xxxxUsername : xxxxx
Classname : vB_Database
MySQL Version :

**borbole** · Thu 21 Jul '11, 7:41am

MySQL Error : MySQL server has gone away

This is a host related issue. You should talk to them.

**George L** · Thu 21 Jul '11, 5:58pm

The problem is some of your vB tables were created or converted to InnoDB storage engine from the usual MyISAM storage engine which you can read up on why you would want to use or not use InnoDB over MyISAM at http://vbtechsupport.com/675/

Now the problem I am guessing is your web host has InnoDB storage engine enabled by default without innodb_file_per_table option set from the start when they enabled InnoDB storage engine support. What this means is you have a shared InnoDB table space for all MySQL databases on the server. Now if InnoDB table gets corrupted it can potentially bring down all InnoDB tables from any database of the server which has been converted or created using InnoDB.

Every table which shows below message suggests they are InnoDB storage engine format and not MyISAM as InnoDB doesn't support the usual REPAIR/OPTIMIZE table commands which MyISAM does (one of the many difference which I outline as 'needing to know' at http://vbtechsupport.com/675/ if you decide to continue using InnoDB tables.

Note: Table does not support optimize, doing recreate + analyze instead

My suggestion is convert all your InnoDB tables back to MyISAM using my guide at http://vbtechsupport.com/675/. Bottom of page has specific example of how to do this if you ssh2 telnet access. But as you're on shared hosting, you will need to get your web host to do this for you.

As to your corruption killed queries could your web hosts practice or limiting resource usage ?? no idea if that is the case but if it is, then that is what is causing corruption as queries are killed prematurely corrupting your data. I suggest you find a new web host as hostgator ain't know to be generous for their shared hosting resource allocations.

HTH

**fccsonline** · Wed 27 Jul '11, 5:08pm

Thank you, that is very helpful! I'll see if their support will help me out with this since it is a shared account. I could always go back to a VPS but that came with more responsibility that I simply don't want any longer.

**George L** · Wed 27 Jul '11, 6:19pm

You're welcome

**fccsonline** · Thu 28 Jul '11, 4:37am

I get the impression they didn't even read the ticket where I requested help converting the tables since I do not have shell access...

Hello,

After talking this over with my manager to see what we could do about this issue. We cannot adjust our kill scripts as they are not per user they are based off the server.
The only thing that we can suggest is to move to a VPS server or change form software, currently we have no problem with another form software other then Vbulletin
as they do not have the best of optimized queries. We are sorry that there is nothan more that we can do to help you as it was suggested to index the tables, but upon
further investigation the "select *" query is not the best way and will probably still hit our kill scripts.

Best regards,

Will M.
Linux Systems Administrator
HostGator.com LLC
http://support.hostgator.com

I realize that a VPS is an option and it is in the budget, but now I'm just pissed and don't want to give them more money. I'll probably get over it and do so, though.

**bszopi** · Thu 28 Jul '11, 4:53am

Originally posted by fccsonline

now I'm just pissed and don't want to give them more money. I'll probably get over it and do so, though.

I wouldn't use HostGator's VPS service, either. There are plenty of other VPS services out there. As to your previous remark about a VPS requiring more responsibility, not sure where you are getting that. I went from shared hosting to a VPS, and other than now having shell access, I didn't see any other differences in responsibilities. I have the ability to do A LOT more now with the server, but it doesn't mean I have to.

**fccsonline** · Thu 28 Jul '11, 8:14am

I know there are cheaper hosts out there - but overall I've been VERY impressed with Host Gators responsiveness to the matter. WHile I wish they allocated more resources, it is a small shared account, so it is what it is. Anyway, they converted the tables for me within an hour of my request - I kind of expected them to force me to a VPS but they didn't. So far if I need it, wi"m willing to pay a bit of a premium for their VPS or dedicated servers just for the fact that they respond politely and quickly to requests.

Thank you for your update regarding this issue and I deeply apologize for any inconvenience and understand your concern. It isn't uncommon to see issues such as this arise on a shared box and amongst all of the Forum software that is offered we do see issues such as this across the board. Unfortunately database driven sites usually are effected the most when it comes to shared servers and sometimes require some attention in optimizing them to work well with our configuration.

Generally converting the Engine type for a mySQL database is unsupported and is generally not allowed on our shared servers. Settings such as these usually require for the customer to own their own configuration by either purchasing a VPS or a Dedicated Server solution. However in this case we have made an exception and went ahead and ran the commands to alter the Engine type to MyISAM. After working with a upper tier administrator we both confirmed that the commands ran successfully (Screen shot attached to show Engine type) and mySQL was restarted to ensure these changes hold.

Please do keep in mind although the storage engine was changed this doesn't necessarily mean you won't end up hitting our kill scripts. If you continue to hit the kill scripts, I would highly recommend a custom solution such as a VPS or a Dedicated Server.

If you have any further questions or concerns please do let us know and we will be more than happy to assist you further.

Best wishes,

Rob T
Linux Systems Administrator
HostGator.com LLC
http://support.hostgator.com

**setishock** · Thu 28 Jul '11, 8:27am

Shop around and play them off each other to get the best package at the best price. And lock them in for a year. Takes a little time and can get quite funny at times but is well worth the investment.

**George L** · Thu 28 Jul '11, 9:44pm

Originally posted by fccsonline

I get the impression they didn't even read the ticket where I requested help converting the tables since I do not have shell access...

I realize that a VPS is an option and it is in the budget, but now I'm just pissed and don't want to give them more money. I'll probably get over it and do so, though.

not really a vB query optimisation issue (excluding any vB add on plugins you install) but more so how their shared server's mysql is setup and configured. But yes looks like VPS is only way to get full access and control to all your settings. Moving to VPS doesn't necessarily mean you have more resource requirements but some folks do so for getting full root access and better control over how their server and it's settings are configured.

But looks like they confirmed their kill scripts are what is causing your database corruption !

vBulletin 4 End of Life

Database corruption keeps occuring

[Forum] Database corruption keeps occuring

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Related Topics