This is different with the preceding 2 ways that can return back the log information for all databases. The sys.database_files catalog view has information for data files and log file of the current refferenced database. Although I calculated the log usage percent, it has indeed a count name 'Percent Log Used' for the sys.dm_os_performance_counters view, but it has no decimal points for the percent value. If you only concern one database then you can limit the database name in instance_name. Select instance_Name as Database_Name, counter_name, cntr_value as Log_Size As I only concern the log file size for this purpose, I use the script below to monitor the log space usage: Select Database_Name This view keeps the records of the log file size and also data file size as counter name for all databases. The second and less commonly used technique to monitor the log space usage is to use the sys.dm_os_performance_counters dynamic management view. , Log_Size_MB * Log_Used_Percent / 100 As Log_Used_Size_MB Insert Into ('DBCC SQLPERF (LOGSPACE) ') The script below is one example which can give you the log space information programtically by using DBCC SQLPERF(LOGSPACE): Declare Table ( However, if you want to progmatically use the information output by the DBCC command, then there is a little bit work to do.

This script is very simple and straightforward to use.

Typically, we use DBCC SQLPERF(LOGSPACE) to monitor the log size and percent of space used for all databases. This is also true for monitoring the database log size and its usage.

In SQL server, there are often different ways to achieve the same goal.

Adventureworksdw2012 database download