You have a server that has very limited memory but has a very large table. You will use mysqldump to back up this table. Which option will ensure mysqldump will process a row at a time instead of…

The correct answer is C. --quick. --quick instructs mysqldump to retrieve rows one at a time directly from the server using mysql_use_result() instead of fetching the entire result set into memory with mysql_store_result() - this is critical when memory is constrained and the table is large. --tab outputs data…

Backup and Recovery

Question

You have a server that has very limited memory but has a very large table. You will use mysqldump to back up this table. Which option will ensure mysqldump will process a row at a time instead of buffering a set of rows?

Options

A--tab
B--single-transaction
C--quick
D--skip-buffer

How the community answered

(52 responses)

A
2% (1)
B
2% (1)
C
90% (47)
D
6% (3)

Explanation

--quick instructs mysqldump to retrieve rows one at a time directly from the server using mysql_use_result() instead of fetching the entire result set into memory with mysql_store_result() - this is critical when memory is constrained and the table is large. --tab outputs data as tab-separated files per table, which is about output format, not memory management. --single-transaction issues a BEGIN statement to get a consistent snapshot for InnoDB tables - it addresses data consistency, not memory buffering. --skip-buffer is a fabricated distractor; no such mysqldump option exists.

Memory tip: Think "quick = no waiting to buffer" - --quick lets mysqldump process and write each row immediately rather than holding the whole result set in RAM before writing anything.

Topics

#mysqldump#memory management#backup options#row buffering

Community Discussion

No community discussion yet for this question.

Full 1Z0-888 Practice