RE: ibdata size
Armando <[email protected]>
| Newsgroups | gmane.comp.db.mysql.windows |
|---|---|
| Message-ID | <[email protected]> |
Yes, OPTIMIZE works on InnoDB, however post v4.1.3 it's been mapped to ALTER TABLE. It's in the documentation and very easy to find. Cheers. Armando ------------------------- In case of MYISAM tables, we do OPTIMIZE table after deletion of records from a particular table. This will free up the disk space for that particular table. I hope the same case might work for innodb tables. Ila. -----Original Message----- From: Urcid Pliego, Paulo [mailto:paulo.urcid@stripped] Sent: Wednesday, June 07, 2006 9:45 AM To: win32@stripped Subject: ibdata size Hi everyone! We have an InnoDB database with its respective ibdata file. As you probably know, the ibdata has a fixed initial size and may grow as more data is stored in the database. Curiously, when we delete data from the database, the size of the ibdata doesn't get smaller. I have searched forums and the mysql web site and found that this is not a bug, its just that InnoDB was designed that way. So, when we are about to run out of disk space, we have to dump the current data, erase the partition where the ibdata files are, recreate them with a smaller size, and finally load the dump back in. Has anyone encountered this situation? Does anyone have a different approach to this? I welcome any feedback!! Thanks for your time Paulo Urcid Pliego E-Labor Producción DM e IM Preserie y Construcción de Equipos Volkswagen de México S.A. de C.V. Teléfono +52 (222) 2 30 9961 Fax +52 (222) 2 30 6082 <mailto:urcid@stripped> mailto:urcid@stripped <http://www.vw.com.mx/> http://www.vw.com.mx -- MySQL Windows Mailing List For list archives: http://lists.mysql.com/win32 To unsubscribe: http://lists.mysql.com/[email protected]