Why are dumps so unreliable?
I have a daily dump of my database, with the single dump file now totalling 220mb uncompressed. What astonishes me though, is how unreliable the dumps are.
Correct me if i'm wrong, but *surely* if MySQL is able to generate a dump file of SQL statements to rebuild the current database, then they *should* execute flawlessly when doing an import.
Why is it, that 90% of the time when I recover from a dump I have to manually edit my dump file because I am almost certain to get errors in the SQL execution at several places in the dump file?
The most notable problems are in the reconstruction of triggers, but I also have problems in even some basic statements such as inserts or table definitions.
Am I doing something wrong or is MySQL just not of production quality yet?
On a side note - how does one edit the 200mb dump file when it basically hangs pico and brings 'vi' to an insufferable crawl. Is there a good set of tools for cutting buts out of dump files, or importing only certain parts of it?
Thanks!
Terence
Subject
Views
Written By
Posted
Why are dumps so unreliable?
2971
May 12, 2006 01:15PM
2148
May 12, 2006 01:35PM
2186
May 12, 2006 02:12PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.