Posted by Surfer! on 03/08/06 15:03

In message <yrmdnaY-s71OTZPZRVn-rg@comcast.com>, Jerry Stuckle
<jstucklex@attglobal.net> writes
<snip>
>
>But it may not be the data which is cached, either. It might be the db
>server has been swapped out, or any number of things. I really
>wouldn't expect a different db server to act differently - because I
>don't think it's a MySQL problem.
>
>But since you're on a shared host, there's no way for you to
>troubleshoot the problem. Have you tried talking to your hosting
>company's support group? And if they can't help you, find a competent
>hosting company.

Has the OP tried this at home? E.g. if he has a PC at home set up with
the same database & scripts, does he have the same problem? If not then
in my view that points the finger at the hosted database, but if he has
it at home them maybe it *is* the query tuning etc.

BTW is he *sure* that the schemas of the two databases are identical?
It's not unknown for people to create indexes on test databases to
resolve performance issues and then forget to create them on the live...
:)

--
Surfer!
Email to: ramwater at uk2 dot net

[Back to original message]