>>>>It is obvious to me that I am able to write "through the cache" on the server (as MS puts it) from a client machine using FILE_FLAG_WRITE_THROUGH (just like SQL Server does).
>>>
>>>Well I can't tell for sure. I see FILE_FLAG_WRITE_THROUGH as applicable ONLY in the CreateFile, so it seems applicable to all WRITE I/O to the file. I was reading about FlushFileBuffers and it seems more applicable for FLUSH, at least as I understand things.
>>
>>I'll take one or the other. If I was asking for the "community" in general, I would ask for FILE_FLAG_WRITE_THROUGH which imposes less of a responsibility (to "flush") on the application programmer. A compromise could be both, with a "toggle" for opening files with FILE_FLAG_WRITE_THROUGH.
>
>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...
>
>cheers

Jim (and Gerry),

While the concept of a global, or even a file-specific FILE_FLAG_WRITE_THROUGH flag sounds useful, I wouldn't regard this as a satisfactory substitute for a functioning local FLUSH command. By the same token, I don't think disabling Windows write caching altogether is a reasonable substitute. In many contexts, these would be either too incomplete, or too heavy handed. Getting back to the original wish that started this thread, I believe it should stand as originally stated.

Mike