Cannot Synchronize All Tables!

[motin]

I have a database with about 60 tables. On the target side (locally) I have only the schema, as I want to transfer the whole database.

7 of them produces (one at a time), when trying to synchronize, XP send error report dialogues, and sync is stopped (even though I have no abort on error checked). I then have to re-run it with that table unchecked for sync and then it will run to the next impossible table with the same results.

There is one common factor, these tables are the largest, containg 134350, 15786, 31573, 80623, 4166, 229915, and 3662 number of rows.

(although another table with 9474 rows passes through the sync)

Is there a limitation to how large the tables can be together with the use of http tunneling?

How can I debug this manually to give a better error report?

I have made the following observations:

-The small tables of above, with 4166 and 3662 number of rows, passes through sync if done alone i a job!

-For every other problematic (large) table, the sync starts out fine. Watching sja.exe's memory and cpu usage while syncing always has this trend: slow but steady memory and cpu usage from about 12mb 30% to about 18mb 80%, then all of a sudden, in 2-3 seconds the memory gets about 40-60mb, cpu usage 97% or more, and then the error report dialogue box.

What should I do?

[motin]

I always do a search in forums before posting, but still I managed to doule-post. Searching for “large tables” gave me a post that addresses the same issue.

Highlights:

Quote:

My theory is that if I can get them copied the once then synch should be ok as there are minimal differences to deal with.

&&

Quote:

For a big table, it is recommended that you import the data in the target server for the first time and then sync it.

Now I know what to do: Import the data through standard methods instead of the Synchronization Wizard. Then use the wizard for what it is made for: synchronization!

[peterlaursen]

It might be an issue with php configuration.

From my own php configuration file I quote these settings:

Quote:

max_execution_time = 30    ; Maximum execution time of each script, in seconds

max_input_time = 60 ; Maximum amount of time each script may spend parsing request data

memory_limit = 8M      ; Maximum amount of memory a script may consume (8M:cool:

And my experience is that the “cheaper” ISP's are not generous with that!

[Ritesh]

It is a known issue with HTTP Tunneling when we try to import large tables (with lot of rows). Since, HTTP is stateless we have to populate the whole table data at the source computer and due to limit specified in PHP configuration, it fails. 🙁

We plan to fix this issue in v4.3. Another SQLyog user has reported the same problem and thus requires more attention.

As of now, you will need to create a dump of database at source in SQL statements. Import it locally using Tool -> Import SQL Statements. Once, a locally copy of the db has been made, you can use Sync feature without any problem.

[Author]

Posts