This is a good general indicator of performance problems. High stall times indicate I/O problems, which can be attributed to busy physical disks or queries that return large data sets to the client.
2015-05-26
6,171 reads
This metric collects the number of 8-kilobyte pages that make up the plan cache to help identify memory pressure or plan cache pollution. A sudden drop in values for this metric may indicate that the instance is under memory pressure and SQL Server had to reclaim part of the plan cache for other use.
2015-05-06
7,382 reads
This alert is raised when the number of hash warnings events in the last hour goes above a specified threshold. A hash warning event means that part of the data processed for a hash operation was written to tempdb during query execution, which can degrade SQL Server Performance.
2015-03-31
6,894 reads
If your code uses temporary tables, variable tables or dynamic cursors, this metric can help identify whether you have contention on tempdb allocation. Tempdb is shared by all databases and is used for many operations in a SQL Server instance, so it is common for tempdb to cause performance problems.
2015-02-17
8,580 reads
This metric can help if you want to monitor the number of indexes per database that haven't been used for the last month. Indexes that aren't in use should be removed because they can degrade INSERT, UPDATE and DELETE performance, and they use storage space.
2015-02-04
2,179 reads
This is a general indicator of performance problems. Index fragmentation can affect the rate of return for moderate to large tables. If this value indicates an increased amount of index fragmentation throughout your database, you may need to fine-tune your indexes by redesigning, or rebuilding more frequently.
2015-01-22
7,455 reads
If your application relies on identity columns, this metric is a useful measure of the number of identity columns that are near to the limit per database. You can then avoid logical problems in your application and SQL Server errors.
2015-01-06
6,226 reads
This metric picks up excessive counts of Virtual Log Files (VLF) in a transaction log that can lead to performance problems, including write performance, restore and recovery times. The ideal value for this metric should be less than 25; excessively high values (greater than 50) can cause high write times when writing to the transaction log.
2014-12-11
7,312 reads
This metric is a great general indicator of performance problems. High stall times indicate I/O problems, which can be attributed to busy physical disks or queries that return large data sets to the client.
2014-10-28
7,321 reads
Trying to determine if you have pressure in your buffer allocations can be difficult. This metric reliably indicates if you have a buffer problem using the memory dump from DBCC MEMORYSTATUS() and comparing Target Committed to the Current Committed allocations. If you hit negative numbers you are looking at a buffer issue.
2014-10-14
6,901 reads
By Steve Jones
One of the neat enhancements made to Flyway was the addition of state-based workflows...
I did a couple of posts previously on dumping/restoring Azure PostgreSQL databases and also...
By Brian Kelley
Most of us know that spending a lot of time on social media and...
Comments posted to this topic are about the item Resolving Access Denied Errors During...
Comments posted to this topic are about the item The Lesser Used Functions
Comments posted to this topic are about the item SQL in an Azure VM...
If I use the Azure Backup service for automated backups of my SQL Servers in Azure VMs, how often can I configure log backups? (as of Dec 2024)
See possible answers