While I can appreciate the intent and I don't know if this is true for XP Embedded...Windows in general is not considered robust in the event of repeated power cuts. As I understand it, Windows was not designed nor intended for such an environment.
If the device is subject to frequent random power outages, you may want to consider an operating system intended for such a situation...though off the top of my head I cannot name one. Every operating system I can think of "prefers" a controlled shutdown to ensure proper completion of minor tasks such as disk writing. For Windows, if the power goes off in the middle of a critical operation, its a crap shoot as to whether or not the machine will even boot the next time you try...albeit the odds are very good that it will. But the recommendations I have read are to run a chkdsk after a power failure to ensure the disk itself isn't corrupted. FWIW John Elrick Calamani, Olga wrote: > Yes I do! and I clearly understand that is not possible to eliminate > corruption problems, but I'd like to set up the system in the best way ... > > Olga > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of D. Richard Hipp > Sent: mercoledì 1 ottobre 2008 17.12 > To: General Discussion of SQLite Database > Subject: Re: [sqlite] Power Loss and database files corruption > > > On Oct 1, 2008, at 10:41 AM, Calamani, Olga wrote: > > >> Hi, >> >> I' m trying to set up a system using SQLite with ODBC interface on >> Windows XP Embedded and trying to understand which types of actions I >> have to do on my software to prevent data corruption during a power >> loss. >> >> I set up a test system writing continuosly on database ( transactions >> with 4 insert each one ) and stopping it with power losses. After 100 >> stops task did not work properly because a rollback was performed on a >> table ( this can be managed changing sotware). After others 20 stops >> database was corrupted with "database disk image is malformed". >> >> I want to try same tests with PRAGMA journal_mode=PERSIST and try to >> understand how and if the corruption frequency depends on file >> dimension. >> >> Do you have other suggestions? >> Any help would be appreciated >> >> > > Have you read this document: http://www.sqlite.org/atomiccommit.html > > D. Richard Hipp > [EMAIL PROTECTED] > > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > > This message (including any attachments) contains confidential > and/or proprietary information intended only for the addressee. > Any unauthorized disclosure, copying, distribution or reliance on > the contents of this information is strictly prohibited and may > constitute a violation of law. If you are not the intended > recipient, please notify the sender immediately by responding to > this e-mail, and delete the message from your system. If you > have any questions about this e-mail please notify the sender > immediately. > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - http://www.avg.com > Version: 8.0.173 / Virus Database: 270.7.5/1702 - Release Date: 10/1/2008 > 9:05 AM > > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
