Hi,

> I'd like to see what Phil reports with respect to his testing on Win2K
> before making a real issue of this...

>
>I imported about 200Mb into an empty database on each machine, and I left
>both machines 'idle' for 2 hours after the import process. On Machine 1, I

>pulled the power cord, on Machine 2 I closed down the client app's database

>connection, and pulled the power cord. On reboot, Machine 1 had an empty
>database, Machine 2 had all the data.

>This seams to me that Windows is not flushing the changes to the file until

>after the database connection has been closed.

Well, if Windows flushes after the file handle is
released/closed/whatevered, this seems logical. Closing the last connection
makes the server close the file handle, hence the flush.

Personally, if this is a problem with the Win servers, I would say:
background thread the flush periodically at a user/sysdba defined interval.
Perhaps this can be overridden per database (like BUFFERS) - the sysdba/db
owner can then decide when this flush is happening, depending on the
performance degration this is going to cause. Perhaps it should be like the
sweep: every x transactions?


Comments anyone?


Martijn Tonies
InterBase Workbench - the developer tool for InterBase and Firebird
http://www.interbaseworkbench.com


[Non-text portions of this message have been removed]