Note that there are some explanatory texts on larger screens.

plurals
  1. POAutomatic Database backup formatted for BigDump
    text
    copied!<p>I'm wanting to do daily backups of my MySQL database, that can be restored using BigDump, as one of my tables has over 4,000,000 records. The issue is, it can't use extended inserts, as explained on their <a href="http://www.ozerov.de/bigdump/usage/" rel="nofollow">website</a>.</p> <blockquote> <p>Note 1: BigDump will fail processing large tables containing extended inserts. An extended insert contains all table entries within one SQL query. BigDump isn’t able to split such SQL queries. In most cases BigDump will stop if some query includes to many lines.</p> </blockquote> <p>I'm trying to create an SQL dump from a ChronJob so that it is compatable with this script? From their FAQ page you can get the required results manually with phpmyadmin:</p> <blockquote> <p>In the older versions of phpMyAdmin look for extended inserts switch in the export settings and set it to off. In the newer phpMyAdmin versions select Include column names in every INSERT statement for Syntax to use in the Data dump options of the export dialog.</p> </blockquote> <p>Can anyone help me out with the PHP to do this? I am not experienced in using shell commands at all! I've tried to follow the mysqldump <a href="http://dev.mysql.com/doc/refman/5.1/en/mysqldump.html" rel="nofollow">docs</a> Here's what I got already:</p> <pre><code>&lt;?php set_time_limit(86000); include($_SERVER['DOCUMENT_ROOT']."/pagetop.php"); $db = new dbsettings; $filename = date("d-m-Y"); exec(" mysqldump --user=".$db-&gt;username." --password=".$db-&gt;password." --host=".$db-&gt;hostname." --add-drop-database --add-drop-table --skip-extended-insert --disable-keys --add-locks --force ".$db-&gt;databaseName." &gt; /backups/".$filename.".sql "); ?&gt; </code></pre> <p>Am I missing any arguments that should be used? And is my exec syntax correct? Thanks for any insight</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload