Not having a Windows Server 2016, I don't really know if the OPLOCKS issue still applies or not. We're still on WS2008R2.
Fred
On Tue, Jun 6, 2017 at 9:20 PM, <mbsoftwaresolutions@mbsoftwaresolutions.com
wrote:
On 2017-06-06 17:18, Fred Taylor wrote:
Sounds like a caching issue.
My thoughts too; however, the write-behind caching is turned off on the CLIENT. I *do wonder* however about the Windows Server 2016 write-behind setting. Is this related to the OpLocks setting mentioned in past server versions?
[excessive quoting removed by server]