2013/2/15 Reindl Harald <h.rei...@thelounge.net> > "our database is 400 GB, mysqldump is 600MB" was not a typo and you > honestly believed that you can import this dump to somewhat? > > WTF - as admin you should be able to see if the things in front > of you are theoretically possible before your start any action > and 1:400 is impossible, specially because mysql-dumps are > ALWAYS WAY LARGER then the databasses because they contain > sql-statements and not only data
That's not completely true. If you have a poor maintained database or just tables with lot of writes and deletes and you don't periodically optimize it - you can end up with lot of blank spaces in your tables which will use _a lot_ of space. If you do a "du" or whatever to measure your database size...you can get really confused. mysqldump obviously doesn't backup blank spaces and once you get rid of them, your database will use much less space. I have seen this scenario many times and I have seen tables using like 30GB disk space and after an "optimize" their reported disk size would be just 5-10GB. Manuel.
