Author: ItaitaiItaitai
Date: Dec 24, 2007 05:56
Hi
I'm dealing with an application that extracts records from a high-
volume log file. I'm trying to figure out a way to minimize extracting
the same records in case the application crashes (the application
knows how to deal with duplicates but its high cost).
I'm thinking about maintaining a "last record pointer" that would be
updated upon successful read(s) and persisted to disk. My concern is
that the file holding the pointer might get corrupted as well and I
will have no way to know from where to continue.
We are using Win2k3 and Windows 2008 transactions are currently not an
option.
I was thinking about maintaining the pointer in SQL Server, since it
support transaction, but it seems overkill.
Is there any writable storage in Windows which support transactions?
Does the system registry have any mechanisms that safeguard from data
corruption?
Thanks!
-Itai
|