{"name":"Last full backup size (MB)","description":"The size of the last Full Database backup for each database, in MB. When reviewing the analysis graph, look for large, steep rises or falls that indicate rapid changes in size. \r\nFor example, you might expect backup size to track data size so potentially on a slow upward trend over a long time with seasonal drops relating to when data is archived. \r\nMonitoring system databases means that you can check to see if anyone accidentally creates a table in Master and fills it with data because they didn\u2019t change their default database setting.","tsql":"SELECT TOP 1 [b].[backup_size] \/ (1024 * 1024.0) AS [LastBackUp_MB]\r\n  FROM [msdb].[dbo].[backupfile] AS b\r\n  INNER JOIN [msdb].[dbo].[backupset] AS b2\r\n  ON\r\n    [b].[backup_set_id] = [b2].[backup_set_id] \r\n  INNER JOIN [sys].[sysfiles] AS s\r\n  ON\r\n    [b].[logical_name] COLLATE DATABASE_DEFAULT = [s].[name]\r\n  WHERE [b].[file_type] = 'D'\t-- Log backups have a file-type of 'L' but will have a range of sizes.\r\n  ORDER BY [b2].[backup_start_date] DESC;\r\n-- If you have a mixture of collations on your server you will need to build this join using a COLLATE value to JOIN to MSDB e.g.;\r\n-- if MSDB has a collation of Latin1_General_CI_AS you will need to write the join as \"ON [b].[logical_name] = [s].[name] COLLATE Latin1_General_CI_AS\"\r\n","instances":true,"frequency":3600,"databases":{"mode":0},"rateofchange":false,"metricenabled":true,"noalertremark":"Setting an alert on this is difficult as the starting size of the database has to be known and as such the alert will then need to be specified for every database.","alertdescription":"","aboveorbelow":"above","collections":1,"alertenabled":false,"_thresholds_high":{"selected":false},"_thresholds_medium":{"selected":false},"_thresholds_low":{"selected":false},"frequency_comment":"Note: This needs to follow your backup schedule. Probably no more frequent than every 30 minutes but potentially daily would be acceptable.","targetentitytype":0}