MySQL Forums
Forum List  »  InnoDB

Re: Mysql database size when exported
Posted by: Rick James
Date: June 25, 2016 09:54PM

It cannot be predicted. For example...

INT takes 4 bytes in the database, but the value '0' will take 2 bytes in the dump ('0' and ','), whereas '-2000111222', which fits in INT will take 12 bytes. ENUM and SET expand significantly. VARCHAR, unless the text is non-ascii will not expand much (mostly two quotes and one comma). Etc, etc.

So, the factor of 1.6 that you got is within the what can be expected.

Consider piping the output to some compression package (zip, etc); that might shrink the result by a factor of 3.

Options: ReplyQuote

Written By
Re: Mysql database size when exported
June 25, 2016 09:54PM

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.