This metric tells you how many database pages are currently being occupied in the data cache. The higher the buffer manager: database pages is, the less room there is for SQL Server to cache more data pages. Read more
This metric measures the total number of one-time use ad hoc queries in the plan cache that have been stored in the form of a stub, not as a full execution plan. Read more
Knowing how much of your RAM is committed to each database can help you provision the right amount of RAM to SQL Server. It also helps to identify rogue queries that draw too much data into RAM and force data from other databases out of the cache. 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
by Redgate Monitor Team | 6,311 views | Performance
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
12,163
0
