WHY WHY WHY, it always happens like this. I do backups of my db once every few days, never ONCE encountered a problem. Well, tonight, I announced to everyone I was moving to our new dedicated server at midnight. <br /><br />So, I closed the forums, went into SSH and typed my typical mysqldump command.. and get this!!!!<br /><br /><pre><font class="small">code:</font><hr>mysqldump: Out of memory (Needed 8164 bytes)<br />mysqldump: Got error: 2008: MySQL client run out of memory when retrieving data from server</pre><hr><br /><br />AHHH!!!!! I should have been already live and on my new server, but this all of a sudden happens. Never once in over a year seen this problem, and of course it happens at the worst possible time.<br /><br />So, just wondering, will this go away when the server starts using less ram, or is it one of those things the server may need a reboot to free everything up? Last time a server with this host crashed they disabled my database saying it was my fault! I just want to get my DB off from their server and run, I'm sick of this crap. <img src="/forum/images/graemlins/frown.gif" alt="" />

Wow, that was stupid. I was up until 4am waiting for it to work, trying other methods... NOTHING. So I go to bed, wake up first thing and try again, it still didn't work!<br /><br />finally, for fun I tried using the --quick flag. And WTF it worked! (I think) I tried the word quick as a joke, then after looking it up it may have really been what I needed *shakes head*

That could make sense.<br /><br />The mysqldump documentation says Note that if you run mysqldump without --quick or --opt, mysqldump will load the whole result set into memory before dumping the result. This will probably be a problem if you are dumping a big database.<br /><br />The description for the --quick option is Don't buffer query, dump directly to stdout. Uses mysql_use_result() to do this.<br /><br />I use the following options for backups: --quick --add-drop-table --add-locks --lock-tables.<br /><br />The --opt option, as suggested by the MySQL manual, includes all of the above options with the addition of --extended-insert (Use the new multiline INSERT syntax, for more compact and faster inserts statements.). I omit the --extended-insert option since it makes it more difficult to view or edit the dump file with a text editor, should that be desired.<br /><br /><br />