While analyzing an issue, I stumbled on to a "FlushCache" error message (error log). There were many (both AM + PM). And this had been going on for quite a while. Had not seen this message before. First instinct was to check other production SQL Servers (VMs) to see if this was happening else where. That was not the case.
Next I checked the server memory, SQL memory, buffer pool and SQL Server max memory. No issues. SQL max memory was more than double the buffer pool. There was adequate memory for the OS as well. BTW - this is SQL Server 2014 SP2 / STD Ed.
Next target / suspicion area is storage. I'm running perfmon right now for both logical and physical disk information.
Any ideas for what could be causing this?
Any comments / suggestions / urls are appreciated.
Sample error log content:
2019-05-14 09:41:49.88 spid15s FlushCache: cleaned up 7506 bufs with 6810 writes in 220866 ms (avoided 5396 new dirty bufs) for db 10:0
2019-05-14 09:41:49.88 spid15s average writes per second: 30.83 writes/sec average throughput: 0.26 MB/sec, I/O saturation: 359, context switches 5417
2019-05-14 09:41:49.88 spid15s last target outstanding: 2160, avgWriteLatency 17