Our monitoring solution (SCOM) is currently flagging that the tempdb log is running out of space. However we have auto grow set to 1GB chunks for the log and we have 25GB of space left on the drive.
I looked at what the
log_reuse_wait_desc was and found it to be
I started to wonder if for some reason the log file was filling up and the auto grow not kicking in, and after some research I found that the log file should still grow even during an
I found an article on a similar issues where the tempdb log ran out of space:
Here they issued a
CHECKPOINT to resolve the issue on
tempdb. I know a
CHECKPOINT flushes dirty pages to disk, however I do not understand how this would fix the
Furthermore I also do not know why we get this alert when there is plenty of space. Is there a situation where a
tempdb can fill and auto grow not work for some reason?