Mysql Windows Innodb Files Beginning With #sql

[Tony]

On Windows Server 2003 running SQLyog Tools->Table Diagnostics->Optimize i noticed mysql creates files beginning with #sql- and ending with .ibd as it copies our innoDB tables. Once optimize is done the #sql files are typically deleted.

For what ever reason I see remnant #sql- files that were not deleted.

Is it ok to manually delete the remnant #sql- .ibd files?

[peterlaursen]

We have no clue really! Actually “OPTIMIZE TABLE” is just a plain and simple SQL statement. Refer http://dev.mysql.com/doc/refman/5.1/en/optimize-table.html . “For InnoDB tables, OPTIMIZE TABLE is mapped to ALTER TABLE, which rebuilds the table to update index statistics and free unused space in the clustered index.”

That simple statement is all we do here. So same issue would happen with any client doing the same. so this question should rather go to MySQL (their Forums for instance) than to us. Maybe some people at MySQL could reply immediately. It could be a bug with a specific server and it could depend on InnoDB configuration settings etc.

We will try to see this for ourselves. I cannot gurantee that it will be before the weekend. It will probably require an installation with some rather big tables.

[peterlaursen]

BTW: maybe you could share your my.ini file? Also please tell exact server version.

[Tony]

Figured these files are temporary files created by mysql as it's doing things like optimize table.

Rather than deleting these files using windows OS, used SQLyog doing DROP TABLE `#sql-108c_53c`;

Did this for each of the #sql- files found in the various mysql data folders.

This does not appear to be related to SQLyog so we can close this thread.

Thanks.

[Author]

Posts