We seem to have a problem that came out of nowhere. The checkpoint process is stuck in SLEEP_BPOOL_FLUSH state, and not actually reducing the usage in the log file.
This never seemed to happen before.
I understand that SLEEP_BPOOL_FLUSH is a normal wait for the CHECKPOINT process when the disk subsystem is busy. Actually, we've always had a very busy disk subsystem so I don't understand why this has become an issue.
(If you manually run a checkpoint command, same results...your user process waits in SLEEP_BPOOL_FLUSH).
Is there ANYTHING we can do to push the checkpoint to occur? Can the parameters for the checkpoint be tweaked so this does not occur?
(SQL Server 2005, RAID subsystem, Simple Recovery Model)