Quote Originally Posted by Jim Mulenos View Post
1) The Database Conversion utility view will freeze mid-conversion once it loses the focus so that progress, though it continues, is not visually apparent. 93 data files and 60GB+ of conversion data took 19+ hours, so this had an impact. The workaround is to follow progress via Workbench.
This is sort of a more general problem in several processes in studio and database builder. Possible the same process information logic. When you reindex in the dbBldr it also stops giving information. Should be fixed.

Quote Originally Posted by Jim Mulenos View Post
2) I would carefully check all type conversions in the Database Conversion utility as Field TYPE conversions are not consistent, specifically with larger (200+ character) ASCII and TEXT fields. The workaround is to check carefully post-conversion what the utility did, and modify as necessary. We changed many post-conversion field types from VarChar to TinyText.
"Played" while being locked in the house in covid restrict time with MySQL. Converting from MsSQL to MySQL. Also was a bit surprised the conversion types used. Conversion did not always work correctly where a certain amount of table could no convert.

Also used MySQL workbench to convert the database. But the SQL created to create the table had all kind of flaws.
Did look at HeidiSQL too, to make it work as easy. But also had issues.



Peter