Dump the entire DB, drop the DB, restore the DB.
On Fri, Feb 11, 2011 at 11:53 AM, Jan Steinman j...@bytesmiths.com wrote:
Our incremental backups seem to be filling with instances of ib_logfile1,
ib_logfile2, and ibdata1.
I know that changing a single byte in a single INNODB table causes
I wrote an article in www.stackoverflow.com about how to convert absolutely
every InnoDB table to .ibd and permanently shrink the ibdata1 file
http://stackoverflow.com/questions/3927690/howto-clean-a-mysql-innodb-storage-engine/4056261#4056261
Enjoy !!!
Rolando A. Edwards
MySQL DBA (SCMDBA)
Thanks, Rolando!
It's kind of a scary procedure (dump, drop, reload) that involves significant
down-time, but I guess it's necessary.
On 11 Feb 11, at 10:24, Rolando Edwards wrote:
I wrote an article in www.stackoverflow.com about how to convert absolutely
every InnoDB table to .ibd and
Hi,
You can convert the tables themselves semi-online. Just do
set global innodb_file_per_table=1;
and no a no-operation alter on each table with alter table tablename
engine=innodb;
Note that the global variable is just a default, the currently connectd
threads will use the shared
