How to determine what cause the temdb database to run out of log space & use 100%?
2018-02-06 09:18 | Success | 1 | WSANETPRA-SQL | tempdb log space is 83.6% used. |
2018-02-06 09:21 | Success | 1 | WSANETPRA-SQL | tempdb log space is 85.0% used. |
2018-02-06 09:24 | Success | 1 | WSANETPRA-SQL | tempdb log space has filled to greater than 85%<c/> so CheckPoint command was run. |
2018-02-06 09:27 | Success | 1 | WSANETPRA-SQL | tempdb log space has filled to greater than 85%<c/> so CheckPoint command was run. |
2018-02-06 09:30 | Success | 1 | WSANETPRA-SQL | tempdb log space has filled to greater than 85%<c/> so CheckPoint command was run. |
2018-02-06 09:33 | Success | 1 | WSANETPRA-SQL | tempdb log space has filled to greater than 85%<c/> so CheckPoint command was run. |
2018-02-06 09:36 | Success | 1 | WSANETPRA-SQL | tempdb log space has filled to greater than 85%<c/> so CheckPoint command was run. |
2018-02-06 09:39 | Success | 1 | WSANETPRA-SQL | tempdb log space has filled to greater than 85%<c/> so CheckPoint command was run. |
2018-02-06 09:42 | Success | 1 | WSANETPRA-SQL | tempdb log space has filled to greater than 85%<c/> so CheckPoint command was run. |
2018-02-06 09:45 | Error | 1 | WSANETPRA-SQL | tempdb log space has filled to greater than 85%<c/> so CheckPoint command was run. [SQLSTATE 01000] (Message 0) One or more recovery units belonging to database 'tempdb' failed to generate a checkpoint. This is typically caused by lack of system resources such as disk or memory<c/> or in some cases due to database corruption. Examine previous entries in the error log for more detailed information on this failure. [SQLSTATE 42000] (Error 5901) The transaction log for database 'tempdb' is full due to 'ACTIVE_TRANSACTION'. [SQLSTATE 42000] (Error 9002) Could not write a checkpoint record in database tempdb because the log is out of space. Contact the database administrator to truncate the log or allocate more space to the database log files. [SQLSTATE 01000] (Error 3619). The step failed. |