Timeline for How can I determine size of database prior to importing from SQL dump?
Current License: CC BY-SA 4.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 22, 2021 at 6:10 | comment | added | Aufgeschissener Kunde |
Output of SELECT @@version is 5.562-0ubuntu0.14.04.1 .
|
|
May 20, 2021 at 23:19 | comment | added | Wilson Hauck | @AufgeschissenerKunde From your MySQL Command Prompt, SELECT @@version; will display the running version of either MySQL or MariaDB. The BEST to you. | |
May 18, 2021 at 0:16 | vote | accept | Aufgeschissener Kunde | ||
May 18, 2021 at 0:02 | comment | added | Aufgeschissener Kunde |
Output of mysql --version : mysql Ver 14.14 Distrib 5.5.62, for debian-linux-gnu (x86_64) using readline 6.3
|
|
May 17, 2021 at 19:21 | comment | added | Rick James | There is no MySQL 14; look elsewhere for the version. | |
May 17, 2021 at 19:20 | answer | added | Rick James | timeline score: 0 | |
May 17, 2021 at 6:03 | comment | added | Akina | There is no a way for to predict the size of the database restored from the dump in practice. Moreover, the same dump restored on different servers with different configuration and settings may differ in size more than twice. For to obtain the most compact representation you may perform OPTIMIZE TABLE for each table in the database after restoring. | |
May 17, 2021 at 3:52 | answer | added | Bill Karwin | timeline score: 1 | |
May 17, 2021 at 2:17 | review | First posts | |||
May 17, 2021 at 10:54 | |||||
May 17, 2021 at 2:13 | history | asked | Aufgeschissener Kunde | CC BY-SA 4.0 |