"Preston Z" <[EMAIL PROTECTED]> wrote: > If the power never goes out and no programs ever crash on you system then > Synchronous = OFF is for you, but the rest of the world might still want it > ON.
Minor clarification: Program crashes will not cause data corruption with synchronous=off. But OS crashes will. As will power failures. > > Are you using transactions where you can? Transactions can speed up things > quite a bit if you have more than one row of data that you are modifying at > a time... personally i would try transactions to speed things up before i > did something as drastic as turning off the sync. Preston's advice is very sound here. Listen to him. > > As for detecting a corrupt database, it won't tell you on opening it that it > is corrupt... it will even execute statements till it hits a piece of the db > that is corrupt (at least the corruption that i have seen, which was from a > bad disk, so might not be the same). There is a symptom of a corrupt > database that i think is almost a sure thing.. run vacuum or dump the > database from the command line tool. If these run OK then you are probably > fine. > > Anybody have a better way to tell if a db is garbage? > VACUUM is good. Also "PRAGMA integrity_check". Note, however, that both commands have to read the entire database file and so can run slowing on large databases. -- D. Richard Hipp <[EMAIL PROTECTED]>
