Large transaction log files

This metric measures the number of transaction log files that are greater than 10 GB. The associated alert is raised when the number of files exceeds the specified threshold.

Install metric...

Metrics install automatically if you have SQL Monitor installed.

If you are using Redgate’s SQL Server monitoring tool, SQL Monitor, you can instantly install and run this metric on your servers.

This metric measures the number of transaction log files that are greater than 10 GB. The associated alert is raised when the number of files exceeds a specified threshold.

If the transaction log autogrows rapidly, it can suggest that log backups are not being carried out frequently enough, or another resource may be preventing the log from truncating.

For more information about autogrow settings, including details on how to check what your current setting is, see Considerations for the “autogrow” and “autoshrink” settings in SQL Server (MSDN).

Large transaction log files, 4.3 out of 5 based on 6 ratings

Metric definition

Name

Large transaction log files

Description

This metric measures the number of transaction log files that are greater than 10 GB. The associated alert is raised when the number of files exceeds the specified threshold. If the transaction log autogrows rapidly, it can suggest that log backups are not being carried out frequently enough, or another resource may be preventing the log from truncating. For more information about autogrow settings, including details on how to check what your current setting is, see Considerations for the "autogrow" and "autoshrink" settings in SQL Server (MSDN).

The T-SQL query that will collect data