I just did that on 1.7 GB INNO table.
It takes ages to decide that id does not suport optimize and then do recreate instead.
Is this waiting to server to respond with "does not suport" ?
Could be done in HeidiSQL I guess, before that.
BTW - if I choose 'accidentaly' to see data tab of table with a lot of data, there is no option to cancel that, I'm doomed to hang around and wait, or kill heidisql process. I think the normal query cancel button should be active at that point, to help me out with that ?
Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.