The DATA SYNC feature will not do this. The purpose of this feature is to bring databases/tables 'in sync' (make them identical). For the same reason STRUCTURE of tables involved must be 100% identical (including column names and columns order). In particular note: the option with this tool does not specify which columns to be sync'ed but only which columns are checked for differences. Complete row will always be synced.
However you could have a look at the MIGRATION tool. With this one you can specify individual columns onand map to any column on . Be careful to understand all the 'advanced' options! Using those options the MIGRATION TOLL will let you sync fromto with INSERTS AND UPDATES. If you have the option to modify theschema use the TRIGGER (refer to FAQ) functionality for efficiency. But the MIGRATION tool will not DELETE rows on – not if they are deleted oneither. That will have to be done manually
But please also note that if the two helpdesk systems use references to other tables in different ways or the applications use some kind of 'trigger code' (for instance for counters like 'no. of times opened') you may mess it completely up. We cannot tell this. Be careful to understand how they both work and ensure good backups!
There is (to my best knowledge) no approved or 'de-facto' standard for how to define/represent a database schema in XML.
Do you have knowledge or ideas of any such standard or convention? Or just good ideas of your own?
Also the (Enterprise) Schema Desingner stores XML already. This .schemaxml contains both information about canvas settings and table definitions. Did you check if the 2nd part of that fullfills your needs?
btw: if you do not click the 'reply' button but the 'add reply' button a little longer down the page the will be a facility to upload files. Images will be displayed as a thumbnail.
We will decide on priorities for 'next shot' after releasing version 6.2 (that enhances the Schema Designer, improves speed, adds support for transactions, makes export/copy operations more flexible + LOTS of minor fixes and request implemented).
“scrolling right to left works fine. Scrolling the other way does not work on large tables”
We know this. We are currently discussing if it is possible to 'promote' this as well as other GRID realated issues into the 6.2 tree. I think we can have the conclusion i about 1 week.
Added: After this “select count(*) from dspam_token_data” returns '13501'
SQLyog 6.16RC – MySQL 5.051a (two databases on the same server on my local).
A can add that I tried copying the 3 first rows toand the first row alone to . They synced correctly (I noticed that `token`had the same value for the three rows.)