From: Nick Khamis Date: November 9 2011 8:32pm Subject: Re: Reusing "ibdata1" space List-Archive: http://lists.mysql.com/mysql/226262 Message-Id: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 wro= te: > Am 01.11.2011 15:02, schrieb Rozeboom, Kay [DAS]: >> We are running MySQL 5.0.77, and using INNODB in production for the firs= t time. =A0The production database has a lot of inserts and deletes, and th= e shared "ibdata1" file is continually growing. =A0I understand that to ret= urn the unused space to the operating system, we must delete and recreate "= ibdata1" and its associated ".frm" files. =A0I am wondering if we could do = the following instead: >> >> 1) =A0 =A0 =A0Let "ibdata1" grow for a while. >> 2) =A0 =A0 =A0Rebuild the tables periodically using this syntax: =A0 ALT= ER TABLE t1 ENGINE =3D 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=3D0" 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 > > >