Re: InnoDB: one big data file or one per table?
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?
Regards,
Rafal
Subject
Views
Written By
Posted
3661
May 17, 2005 03:55AM
3008
May 17, 2005 11:42PM
Re: InnoDB: one big data file or one per table?
2333
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.