> Windows, however, does not keep the filesize (as you would see it in
> Explorer) updated. This is really more of a Windows 'display glitch'
> than an IB/FB problem.
> Equally, if your database and the server were to go *idle* for a little
> while and then the server 'die', I would expect that the database would
> be un-affected/recoverable since the OS would have flushed the pending
> write operations.
I thought that Windows would eventually flush the pending writes to the file
in idle time, but in a test...
- I imported 200Mb of data in to a blank database
- Left the server and client app idle for 4 hours
- Pulled the power cord
...the database was blank after boot up
If I close the client's connection, everything is flushed.
This is not mission critical data, so I can afford to lose a few thousand
reconds, as they can be re-imported, but I can afford to lose 200Mb per Day!
Obviously the easiest solution is to disconnect/connect every hour or so, but
that seams like a bodge to me.
3:43pm up 34 days, 8:53, 1 user, load average: 0.60, 0.43, 0.28