Author: stevestedman

Deadlocks in SQL Server can cause serious performance issues, impacting transactions and slowing down applications. To help database administrators gain deeper insights into deadlocks and resolve them more effectively, Database Health Monitor includes six powerful reports focused on deadlock analysis. These reports provide a server-wide view, per-database breakdowns, historical trends, and object-level details, making it easier to diagnose and prevent deadlocks. 1. Instance Deadlock History Report View Report This report offers a historical overview of all deadlocks that have occurred …

Understanding SQL Server Deadlocks Read more »

Monitoring long-running queries is an essential part of database performance monitoring, as it can help identify queries that are causing performance issues and take corrective action to optimize them. The Database Health Monitor for SQL Server provides insights into long-running queries, enabling you to identify performance bottlenecks and optimize query execution. Blocking Query Monitor: Identifying Performance Bottlenecks in Real-Time One of the primary ways Database Health Monitor tracks long-running queries is through its Blocking Query Monitor. When a query is …

SQL Server Long-running Queries Read more »

Understanding the PREEMPTIVE_OS_CRYPTIMPORTKEY Wait Type in SQL Server Need help with this wait type or others, Stedman Solutions can help. Find out how with a free no risk 30 minute consultation with Steve Stedman. SQL Server uses a wide variety of wait types to track what a query is waiting on before it can continue executing. One of these wait types, PREEMPTIVE_OS_CRYPTIMPORTKEY, can be challenging to understand and troubleshoot. This discussion will provide a deep dive into what this wait …

PREEMPTIVE_OS_CRYPTIMPORTKEY Wait Type in SQL Server Read more »

Here is a short video on managing VLFs Best Practices Best Practices for Managing VLFs Preallocate Log File Size: Instead of allowing SQL Server to expand the log file in small increments, preallocate a sufficient log file size to minimize growth events. Use Larger Growth Increments: Set the log file growth increment to a reasonable value (e.g., 512 MB or more) to avoid creating too many VLFs during growth. Monitor Regularly: Use the VLF Report in Database Health Monitor as …

Managing VLFs Best Practices Read more »

When managing multiple SQL Server instances, database integrity is a top priority. Corruption issues can sneak up unexpectedly, leading to downtime, data loss, or performance problems. One of the most critical SQL Server maintenance tasks is running DBCC CHECKDB, which checks for corruption in your databases. However, running DBCC CHECKDB manually across multiple servers can be tedious and time-consuming. This is where Database Health Monitor comes in—offering a centralized view of DBCC CHECKDB reports across all your instances. In this …

Understanding the DBCC CheckDB Report in Database Health Monitor Read more »

Here is a short video on managing VLFs on SQL Server https://youtu.be/VjsgTWkws8M?si=ywngDBtdL9uE2i0X Best Practices for Managing VLFs Preallocate Log File Size: Instead of allowing SQL Server to expand the log file in small increments, preallocate a sufficient log file size to minimize growth events. Use Larger Growth Increments: Set the log file growth increment to a reasonable value (e.g., 512 MB or more) to avoid creating too many VLFs during growth. Monitor Regularly: Use the VLF Report in Database Health …

What are VLFs and why should you care Read more »