Temporary tablespaces autoextend to satisfy large sorts, hash joins, and global temporary tables. Runaway growth often signals a bad plan or a missing index and can consume the underlying filesystem. Required permissions: GRANT SELECT ON CDB_TEMP_FILES TO redgate_monitor_user CONTAINER=ALL; These are covered by Redgate Monitor’s standard Oracle monitoring user — if it was set up […] Read more
A permanent tablespace that fills up forces Oracle to throw ORA-01653 / ORA-01654 and halts the operations that need space. This metric tracks the used percentage of a tablespace, already accounting for the autoextend maximum, so it reflects true remaining headroom rather than just current file size. Create one instance of this metric per permanent […] Read more
Creating one metric per tablespace works, but a single metric that tracks the worst permanent tablespace in each container covers every tablespace in every PDB — including ones created later — and names the offenders in the alert. Required permissions: GRANT SELECT ON CDB_TABLESPACE_USAGE_METRICS TO redgate_monitor_user CONTAINER=ALL; GRANT SELECT ON CDB_TABLESPACES TO redgate_monitor_user CONTAINER=ALL; These […] Read more
This metric tracks the largest file in a database as a percentage of the maximum file size. If there are 3 files, and 2 are at 50% of the max set (max_usage in sys.database_files), and a third is at 60%, the 60% number is returned. Read more
This custom metric measures the total database file size (data files and log file combined). An increase in this metric signals that a database was grown. When not done by the DBA, this is an autogrow. Excessive autogrow events should be prevented as this can result to file fragmentation. Try to manually grow files before […] Read more
This metric reports the total space used by database files in GB. This includes data files but excludes log files. This lets you track the growth of the databases over time so you can be aware of future space requirements. Alternatively, the following T-SQL can be used for SQL Server 2012 and higher: [crayon-6a8ed0aa9be1e561631214/] Read more
This metric measures the percentage of free space for transaction log files (LDF files). It will also alert you if the amount of free space drops below the specified thresholds. Read more
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. Read more
This metric measures the number of available autogrowth steps for a database, so you can see when they are reduced or increased because something else (e.g. another database) starts or stops taking up space, when storage is added, etc. Read more
What are custom metrics?
The Redgate Monitor custom metric feature lets you run T-SQL queries against your SQL Servers to collect specific data. You can analyze and receive alerts about your custom data just like everything else Redgate Monitor collects.
But what if you don’t want to write your own queries? No problem. Redgate has brought together a range of quality custom metrics for you to use in Redgate Monitor, which are all are free, tried and tested. You can install straight away, and use the resources on this site to help you write your own.
Redgate Monitor is a SQL Server performance monitoring tool that gives you real-time and historical SQL Server performance data with alerts and diagnostics.
With its embedded expertise from SQL Server experts and MVPs, it gives you the information and advice you need to find and fix issues before users are even aware.
This custom metric measures the total database file size (data files and log file combined). An increase in this metric signals that a database was grown. When not done by the DBA, this is an autogrow. Excessive autogrow events should be prevented as this can result to file fragmentation. Try to manually grow files before […] Read more
This metric will display the total number of active backups and restores on a server. This can be used to correlate with other metrics to explain why disk IO and CPU usage could have changed. Read more
11,268
0
