Hello guys,
I have one monster database running on MySQL 4.0.17, using InnoDB:
270GB Oct 10 14:35 ibdata1
I've deleted a lot of register of then, and I've expected that the size
can be decreased if 50% (135 GB) but the ibdata was the same value than
before clean...
How can I force to save
Hi,
Tiago Cruz wrote:
Hello guys,
I have one monster database running on MySQL 4.0.17, using InnoDB:
270GB Oct 10 14:35 ibdata1
I've deleted a lot of register of then, and I've expected that the size
can be decreased if 50% (135 GB) but the ibdata was the same value than
before clean...
/optimize-table.html
-Dan
-Original Message-
From: Tiago Cruz [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 10, 2007 2:14 PM
To: mysql@lists.mysql.com
Subject: Saving space disk (innodb)
Hello guys,
I have one monster database running on MySQL 4.0.17, using InnoDB:
270GB Oct 10 14:35
If you do what Baron suggests, you may want to set Innodb to create a
file-per-table - that way, in the future, you could save space when tables
are dropped, or you could recreate innodb tables individually to save space,
not have to dump all your innodb tables at one time.
On 10/10/07, Baron
Dan Rogart wrote:
OPTIMIZE TABLE should reclaim that space, but be aware that it could
take a while to run (locking your table all the while) since it just
maps to an ALTER TABLE statement which creates a new copy of the table.
Depends on how big your tables are.
Doc:
Thank you guys!!
I have a lot of MyISAM and a lot of InnoDB on this database.
I did one little for to run one OPTIMIZE TABLE in each table that I
have, on my database.
If this step don't save enough disk space, I'll do the Baron suggestion.
Thank you all!
- Tiago Cruz
On Wed, 2007-10-10 at
He's using 4.0, it's not an option in that version :-(
Andrew Carlson wrote:
If you do what Baron suggests, you may want to set Innodb to create a
file-per-table - that way, in the future, you could save space when tables
are dropped, or you could recreate innodb tables individually to save
Hi Tiago,
Tiago Cruz wrote:
Thank you guys!!
I have a lot of MyISAM and a lot of InnoDB on this database.
I did one little for to run one OPTIMIZE TABLE in each table that I
have, on my database.
If this step don't save enough disk space, I'll do the Baron suggestion.
It will not shrink
At 01:24 PM 10/10/2007, Baron Schwartz wrote:
Hi,
Tiago Cruz wrote:
Hello guys,
I have one monster database running on MySQL 4.0.17, using InnoDB:
270GB Oct 10 14:35 ibdata1
I've deleted a lot of register of then, and I've expected that the size
can be decreased if 50% (135 GB) but the ibdata
; mysql@lists.mysql.com
Subject: Re: Saving space disk (innodb)
Hi Tiago,
Tiago Cruz wrote:
Thank you guys!!
I have a lot of MyISAM and a lot of InnoDB on this database.
I did one little for to run one OPTIMIZE TABLE in each table that
I
have, on my database.
If this step don't save enough
Andrew Carlson wrote:
If you do what Baron suggests, you may want to set Innodb to create a
file-per-table - that way, in the future, you could save space when tables
are dropped, or you could recreate innodb tables individually to save space,
not have to dump all your innodb tables at one time.
mos wrote:
At 01:24 PM 10/10/2007, Baron Schwartz wrote:
Hi,
Tiago Cruz wrote:
Hello guys,
I have one monster database running on MySQL 4.0.17, using InnoDB:
270GB Oct 10 14:35 ibdata1
I've deleted a lot of register of then, and I've expected that the size
can be decreased if 50% (135 GB)
Eric Frazier wrote:
Andrew Carlson wrote:
If you do what Baron suggests, you may want to set Innodb to create a
file-per-table - that way, in the future, you could save space when
tables
are dropped, or you could recreate innodb tables individually to save
space,
not have to dump all your
At 02:40 PM 10/10/2007, Baron Schwartz wrote:
mos wrote:
At 01:24 PM 10/10/2007, Baron Schwartz wrote:
Hi,
Tiago Cruz wrote:
Hello guys,
I have one monster database running on MySQL 4.0.17, using InnoDB:
270GB Oct 10 14:35 ibdata1
I've deleted a lot of register of then, and I've expected
14 matches
Mail list logo
