From: Reindl Harald Date: February 16 2013 10:37am Subject: Re: Upgrading form mysql 5.0.90 to 5.5 or 5.6 List-Archive: http://lists.mysql.com/mysql/228996 Message-Id: <511F616D.1050507@thelounge.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2RQDPXXEBPCXOCUGHEASG" ------enig2RQDPXXEBPCXOCUGHEASG Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 16.02.2013 09:42, schrieb Manuel Arostegui: > 2013/2/15 Reindl Harald > >=20 > "our database is 400 GB, mysqldump is 600MB" was not a typo and you= > honestly believed that you can import this dump to somewhat? >=20 > 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 >=20 > That's not completely true. If you have a poor maintained database or j= ust tables with lot of writes and deletes > and you don't periodically optimize it - you can end up with lot of bla= nk spaces in your tables which will use _a > lot_ of space. If you do a "du" or whatever to measure your database si= ze...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.=20 ok, normally i expect there is a admin and doing his job especially for large datasets ------enig2RQDPXXEBPCXOCUGHEASG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlEfYW0ACgkQhmBjz394Ank0YQCfZLXvucKi52ASaXlqzzNVhtxY PZEAn1Cl7knwT34WvPoLf6QfjFHm04S5 =a7PI -----END PGP SIGNATURE----- ------enig2RQDPXXEBPCXOCUGHEASG--