Mayuran Yogarajah [EMAIL PROTECTED] wrote:
Is there some way to trim the 50gb+ file down ?
Yes, dump the databases using mysqldump, then recreate the autoextend
InnoDB tablespace and then run the .sql script.
--
For technical support contracts, goto https://order.mysql.com/?ref=ensita
Currently we have one way master to slave replication setup.
The master has 2 innodb data files, the second has now grown
to 50gb+. The slave's innodb data files are less than 2 gigs.
How is this possible? They are both storing the exact same
data. Is there some way to trim the 50gb+ file down ?
