Chunk Size In Data Sync

[sathish]

 

Please refer this FAQ: http://faq.webyog.com/content/27/114/en/introduction-to-the-_sqlyog-job-agent_-sja.html

 

Data sync jobs additionally supports a ‘-r’ parameter (it is ignored with other types of jobs). It has only an effect when a non-empty source-table is synced to an empty target-table and defines how big CHUNKS should be fetched from source server (for a (source) HTTP connection it is 1000 rows by default if -r option is not specified explicitly). -r2000 (note that the number should not be quoted) will copy CHUNKS of 2000 rows from source. If no -r parameter is specified SQLyog will fetch “all rows” from source server in one ‘SELECT’ query operation what may cause memory exhaustion on the client machine. Also if use (or no use) of the -r parameter results in larger CHUNKS than target ‘max_allowed_packet’ setting on target, this ‘max_allowed_packet’ will still be respected. So in short if your sync job syncs a large non-empty source-table to an empty target-table you could use the -r parameter to control memory consumption on the client. Note that the -r parameter is a command line option only that is not supported from the GUI wizard. 

[osolo]

Thank you.  This is exactly what I was looking for.

[Author]

Posts