[Marco van Herwaarden]

The thing is that advice is not from me but from a guy who has a large Hosting company and deals with Mysql problems almost daily.

And did he also know this is a HEAP table before giving that answer? An expert can only advise based on the information he gets. So gathering all needed info first is essential.

The bonus was he repaired his database and his site was up minutes later.

I think it is a misconception that repairing a database is always a good thing to do. I have seen many cases where repairing a database was causing corruption. If it is needed, you should run it, but if not needed i would not suggest to run it as it can also make things worse.

I'm sorry if i've trodden on your toes here, I know you a technical kinda guy, and very clever too, But the guy was deperate to get his site up and running and with the information i gathered that night, a repair was the best option at that time.

Don't take it too personal. I know i addressed this rant at you, but it could have been anyone. But it is true that it often irritates me when i see people telling members to run certain tasks (often risky) without analysing the problem first. I dont mind if they do so on their own forums, but i don't like it when i see it happen to boards of others.

Yes i do have more technical knowledge then the average (i am for sure not claiming all before someone thinks i feel myself above others) user. But my "complaint" is not really about the technical solutions suggested, but the lack of analysing before making asumptions.

PS You now have explained that you did more analysing then you posted. It does help a lot if you would have posted in your 2nd post: I checked your site, i found this detailed DB-error and the solution is...

Like this you also prevent the next user with a similar problem (ie. "DB-error") thining his error is the same and the solution will be the same.