Hello Reindi, I don't mean to revisit an old post however, we are also using innodb and experiencing a rough start. Should we set innodb_file_per_table to 1? Also we expereince this scenario a lot:
mysql> show tables; +---------------------------+ | Tables_in_symax | +---------------------------+ | acc | ERROR 1146 (42S02): Table 'symax.acc' doesn't exist I should mention that we have deleted the ib_* files in the past. Is it ok if I post our config for a quick review? Thanks in Advance, Nick. On Tue, Nov 1, 2011 at 10:09 AM, Reindl Harald <h.rei...@thelounge.net> wrote: > Am 01.11.2011 15:02, schrieb Rozeboom, Kay [DAS]: >> We are running MySQL 5.0.77, and using INNODB in production for the first >> time. The production database has a lot of inserts and deletes, and the >> shared "ibdata1" file is continually growing. I understand that to return >> the unused space to the operating system, we must delete and recreate >> "ibdata1" and its associated ".frm" files. I am wondering if we could do >> the following instead: >> >> 1) Let "ibdata1" grow for a while. >> 2) Rebuild the tables periodically using this syntax: ALTER TABLE t1 >> ENGINE = InnoDB; > > this will not help as long you are not using "innodb_file_per_table" > and if you would using it "ibdata1" would not grow > > in my opinion "innodb_file_per_table=0" is a dumb default and > requires that people with too few expierience with mysql/innodb > would much more carefully read documentations as they usually do > > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
