[frankf]

This is a huge priority for us, as we are running into performance issues with large tables.

'navyashree.r' wrote:

Hi,

Thanks for your valuable request which is a valid one. We have already in our roadmap about this “Table Partitions” support in our GUI. Please go through our FAQ link,

http://webyog.com/faq/content/33/20/en/plans-for-future-versions-of-sqlyog.html?highlight=future

We have added your request in our issue tracker,

http://code.google.com/p/sqlyog/issues/detail?id=1224

We haven't decided with the priority as we have planned activities for the next 3 to 4 months. Once done we will prioritize accordingly.

Regards,

Navya

[frankf]

Thanks, I did a copy (actually from a dump.. since we create dumps for backup anyway).

By the way, I cannot un-compress the zipped dumps on a Windows 7 server using the default windows zip tool, or Total Commander. I had to start making uncompressed dumps. I am glad I found this out before it became a need.

Tonight we will see how the sync goes. I might need the option for every sync based on the number of inserts each day…

As a feature request, it would be great if the sync options has a checkbox or field to set maximum number of rows to fetch at a time.

'peterlaursen' wrote:

Are you sync'ing to an empty table? If so please read: http://webyog.com/faq/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). -r”2000” 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.”

So please save the job file from the wizard and next invoke it with the -r parameter to the 'sja' command.

(but if you just want to copy (a) table(s) once it is much easier and simpler to 'copy to other' from database or table (context) menu.)

[frankf]

Regarding your comment below, how reliable are your checksum algorithms?

Our database has many updates where the size stays the same (i.e. toggle options, or switching values that are the same length)

For exmaple, if you are only checking if the length of a value changed… changing “positive” to “negative” or 0 to 1 still has the same number of characters, and these are important changes that would be missed.

Would it be something like md5?

'peterlaursen' wrote:

It does not genereate a complete script for the sync job.

It compares a  large number of rows on both hosts using checksum algoritms.  If there is a difference between the two, the beforementioned routine is executed recursively and the individual rows that need to be INSERTed, DELETEd or UPDATED are located.  Next the operations are performed on the rows where it is required, and everything starts over with the next rows until the end of that table has been reached.

Did that answer your question?

[frankf]

Where is the “Export data only” option??

I have the enterprise version and I only see two export options: “structure and data” or “structure only”.

[Author]

Posts