Hello,
I’m using SQLite in one of my applications for several years with great success. The databases managed with SQLite are between 1 and maybe 10 GB, with about 50 tables or so. The platform is Windows 7 or higher. Recently I get an increasing number of error reports about “database disk image malformed” errors from my users. These errors show up out of the blue, with databases held on local hard disks or even SSD’s, no power failures, Windows crashes or anything that’s in the rule book of “How to damage your SQLite database”. The damage is usually detected during “diagnosis” runs. This feature runs an “analyze” and a” vacuum” command in order to physically validate the database (and to optimize and compact it). Are there any settings/options I can check and which are known to increase the likelihood of physical database damage? + I always use the most recent version of SQLite. + I switched to using WAL mode during a larger update about a year ago. + I use syncmode=NORMAL for a good balance between speed and security. + I have PRAGMA wal_autocheckpoint=20000 to speed up bulk inserts (this tip came from drh). + I use nested transactions implemented via checkpoints Anything I need to look for or check? I was under the impression that physical damage is very unlikely and only happens under well-known conditions. Maybe something has changed in recent SQLite builds that somehow causes this to happen more often? I recall that physical damage was really, really rare over the past years – but now I get reports maybe once a week… Thanks for reading and your ideas and comments. -- Mario _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
