It’s important to measure the growth of databases so you can plan future space requirements, prepare for time periods when heavy volume traffic is expected, and take action in advance to prevent problems such as highly fragmented databases. Read more
The metric is a necessary step in order to achieve the key purpose of this metric, which is to create an alert that will be raised when something is added to the schema, or the existing schema is modified. Read more
During a transaction, data is written to the log cache so that it’s ready to be written to the log file on commit, or can be rolled back if necessary. When the log cache is being flushed to disk, the SQL Server session will wait on the WriteLog wait type. 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
This metric monitors whether a server principal's default database is offline. When you create a SQL Server server principal (formerly referred to as a server login) it has a default database setting that is used to assist in a connection request when no database is specified. Read more
If you manage a server where you are not in complete control of the creation of databases, or you’re unfamiliar with what settings to change, you may miss things out or set them incorrectly. Read more
What are custom metrics?
The SQL 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 SQL 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 SQL 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.
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