Yes – the problem is happening with the same data. I only have one version of sqlyog installed.
It happens whether I use the wizard or save the job file and run it from the command line.
Attached are several files compressed in a zip file…
sja from wizard.log – Obviously the log file from running the sync from the wizard
sja from command line.log – the log file from running the sync by doing this: “C:Program FilesSQLyog Enterprisesja.exe” “C:Documents and SettingsPatrick FurgersonMy DocumentsSQLyog ScriptsSync PROD2BACK.xml” -l”C:Program FilesSQLyog Enterprisesja.log” -s”C:Program FilesSQLyog Enterprisesjasession.xml”
sjasession.xml – the .xml file from the above
Sync PROD2BACK.xml – the script file I used from the command line with the same settings as I run from the wizard.
PROD Backup.sql – sql dump of the SOURCE database.
BACKUP backup.sql – sql dump of the TARGET database.
At first I thought it had to do with the fact that on the source database (prod) it seems to allow mixed case table names and on the target database (backup) it does not… so I fixed that problem but then it just hung on a different table.
So I manually copied that table from source to target and then it would work through that table.
But – then when it got down to the original table (though renamed all lower case) it hung again.
