At 28/11/2001 07:22 AM, you wrote:

>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?

This would be a nice feature to add. At the moment I use ForcedWrites=ON,
because the software is distributed in the health care industry, where data
has to be at its safest. And this causes some penalty on the performance
in exchange of consistency and integrity. Having an automatic flush of
data to disk in the background would be useful. Also, if one is to be
implemented, it would be nice to make sure the flush when system shuts down
or if a UPS is connected and a power failure is detected(if the API is
consistent for Windows, I know it might differ from Win9x and WinNT platforms).

This is just my 2 cents.


Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)