[Thrunch]

Thank you for your diligent response Nithin. I have installed your trial version and I have an error log for you that I can send you; however, please email me directly ([email protected]) as I will not post the log to an open forum since it contains a dataset. The data has no identifying information that would make it useful, but there's also no reason to post it here for all to see.

Just to reiterate from my first post, HTTP tunneling is working on every table I've tested except two tables that happen to have 4700 and 27000 records (re-read original post for amplifying details as the problem is 100% replicable). If I synch directly using MySQL (not via the tunnel), the tables synchronize perfectly and completely.

To further verify it is a problem related to the number of records, I tested a synch for both problem tables during which I added a WHERE clause so that they were limited to a 76 row result set (Accounts) and 10 row result set (StudentRecords). In those tests with row counts limited, both problem tables synch via tunneling completely and without error.

With regards to Peter's presumptions on my server … it is Rackspace Cloud which is hardly cheap and cannot be overloaded by such a slight load as this … because it has an entire bank of servers which will dynamically respond to give as much server computing power as needed to meet the load.

Perhaps there is a string limit or post parameter limit you are hitting? I only theorize that because the output SQL in the log is cut off … but that could simply be a limit on the output logging stream.

If you want to send me a version of the PHP with some debug logging parameters, I can easily upload it and that way you can potentially get a monitor of what the server is getting from the SQLyog client.

[Author]

Posts