MySQL Forums
Forum List  »  InnoDB

Re: InnoDB: one big data file or one per table?
Posted by: Rafal Kedziorski
Date: May 18, 2005 01:13PM

development wrote:
> Dear Rafel,


> And if you are also looking for backing up your
> tablespaces, then also file per table concept is
> better. because after some time you will see your
> common tablespace size increased by 30-40 GB,
> which is really very tough for maintain.

thx. I'm thinking about switching to MySQL 4.1.12. Currently I'm working with 4.0.23a. And I preffer innodb_file_per_table. But I'm looking for a good method to transfer our data to the new database.

Is the performance of whole MySQL better or not with innodb_file_per_table?


Options: ReplyQuote

Written By
Re: InnoDB: one big data file or one per table?
May 18, 2005 01:13PM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.