When backing up a largish database (tables with 1000's of records) using the “Scheduled Backup” tool, the resultant .sql file has a corrupt entry after several hundred records. For example:
insert into `classes` (`ClassID`,`ClassDescription`,`ClassCode`,`StudioID`,`GenreID`,`Year`) values (206,'Pre-Elementary A / Pre-Elementary: Saturday, 9.00pm – 10.30am','019',3,1,2003);;
insert into `classes` (`ClassID`,`ClassDescription`,`ClassCode`,`StudioID`,`GenreID`,`Year`) values (
The double semi-colon occurs right before a truncated insert command. The next command is a valid insert. This happens at several places through the file – always with the double semi-colon (;;). The truncated insert is extra to the required inserts, that is, the preceeding and subsequent inserts are correct and should follow each other.