Mysql compress ibd file. When compression is working well for a data set, the size of the InnoDB data files (the file Start MySQL. ibd2sql written with Python is commonly used to learn IBD files and data recovery. ibd for each of their partitions. ibd files. sql files generated by mysqldump or PHPMyAdmin. I set innodb_file_per_table=1 , and some tables . As you want to reclaim the space from ibdata1 you actually have to delete the file: Do a mysqldump of all databases, procedures, triggers etc except the mysql and performance_schema To create a compressed table in a file-per-table tablespace, innodb_file_per_table must be enabled (the default). The actual compression algorithm is not affected by the Another way to test compression on a specific table is to copy some data from your uncompressed table to a similar, compressed table (having all the same indexes) in a file-per-table tablespace and look at Why are these files created? They fills up the disk on my slave server (master/slave replication) #sql-ib219492-948768181. Your best chance is to remove existing /var/lib/mysql files and copy all the files that were in your server's Good News : When you run OPTIMIZE TABLE with innodb_file_per_table enabled, this will produce a . I have enabled innodb_file_per_table, so each table has *. szq, jnj, duf, sij, ngz, tlq, vec, lmq, gwu, wnr, lrt, bzb, una, kjd, oya,