>Yes, after reading your other regarding SQL Server I'd certainly feel comfortable with CreateFile/FILE_FLAG_WRITE_THROUGH. Then FLUSH wouldn't matter.
>I was reticent earlier (still am, a teeny bit) because of performance impact, but if its good enough for SQL Server...

To be on the safe side, FILE_FLAG_WRITE_THROUGH should be an option that you turn on or off (at an application and/or file level), in which case you would still need a FLUSH.

SQL Server does some of it's own "caching" before "writing", much like VFP would do when using TRANSACTIONs.

In a predominately OLTP environment, FFWT would make things simpler.

In a predominately (high-volume) "batch" environment, that did NOT use TRANSACTIONs, there might be a performance problem with FFWT (as your earlier FLUSHING tests may have indicated).