Author: Steve Stedman

Your SQL Server is running hot. CPU is elevated, the plan cache is bloated, and queries that should be instant are taking seconds. You look at the query text and everything seems reasonable. The problem is not what the queries are doing. It is how they are being sent. Non-parameterized queries are one of the most common performance problems in SQL Server environments, and one of the easiest to overlook because the queries themselves often look completely normal. What is …

SQL Code Smells: Non-Parameterized Queries Read more »

Are you struggling with slow database queries or unexpected downtime in your SQL Server environment? At Stedman Solutions, we understand how critical performance and stability are to your business operations. Our SQL Server Performance Assessment is a comprehensive evaluation designed to pinpoint inefficiencies and provide tailored solutions to supercharge your database performance. Through a meticulous process, we dive deep into every aspect of your SQL Server setup, from configuration settings to query execution plans. Our team of experts identifies bottlenecks …

SQL Server Performance Assessment: Boost Speed and Stability with Stedman Solutions Read more »

Features in Database Health Monitor: Job History, Problem Indexes, and Backup Reports At Stedman Solutions, we are always working to make SQL Server management easier and more effective. Database Health Monitor continues to evolve with new reports and enhancements designed to help SQL Server administrators better understand what is happening across their environments. Some of the latest additions focus on three critical areas: SQL Server job activity Problematic indexes Backup visibility and reporting These new features provide clearer insights, faster …

Database Health Monitor Features: Job History Charts, Problem Indexes & Backup Reports for SQL Server Read more »

SQL Server error logs serve as a vital resource for diagnosing performance issues, security events, and unexpected failures within a database environment. When these logs become inaccessible, database administrators lose a primary source of diagnostic information at the exact moment it is needed most. This situation can quickly escalate routine troubleshooting into a prolonged and frustrating process. Common triggers for inaccessibility include oversized log files that exceed practical viewing limits, misconfigured file system permissions, and SQL Server role restrictions that …

SQL Server Error Logs Inaccessible: Causes, Fixes & Prevention Read more »

The Ultimate SQL Server Backup Strategy: Protecting Your Data from Disaster and Corruption In today’s data-driven environments, SQL Server databases often serve as the backbone for critical business operations, making their protection against unexpected failures, data corruption, and catastrophic events a top priority for IT teams everywhere. Many organizations operate without a truly robust backup plan in place, only recognizing the gaps in their approach after an outage or integrity issue has already caused significant disruption and potential data loss. …

SQL Server Backup Strategy: Protect Data from Disaster, Ransomware & Corruption Read more »

The Hidden SQL Server Performance Killer: Implicit Conversions When SQL Server Performance issues begin appearing, many companies assume the only solution is to add more hardware, increase cloud resources, or purchase additional SQL Server licenses. In reality, some of the biggest performance problems come from small development decisions that quietly consume CPU resources over time. One of the most overlooked examples of this is implicit conversions in SQL Server. Implicit conversions occur when SQL Server automatically converts one data type …

The Hidden SQL Server Performance Killer: Implicit Conversions Read more »

Catching Failing Database Health Monitor Jobs with Check 239 Catching Failing Database Health Monitor Jobs with Check 239 One of the most valuable aspects of Database Health Monitor is its ability to watch for issues that might otherwise go unnoticed until they become much larger problems. Check 239 is a great example of this proactive approach to SQL Server monitoring. Check 239 specifically monitors for failing Database Health Monitor jobs. Why Database Health Monitor Jobs Matter Database Health Monitor includes …

Catching Failing Database Health Monitor Jobs Read more »

Are you aware of the true financial burden of managing SQL Server in-house? Many organizations underestimate the hidden costs that go beyond salaries, including tools, training, and the risk of costly downtime. Our latest white paper, “The Real Cost of SQL Server Management: In-House Team vs. Stedman Solutions,” uncovers the full spectrum of expenses and challenges that come with maintaining an internal database team. From hiring skilled DBAs to investing in specialized software, the expenses of in-house SQL Server management …

The Real Cost of SQL Server Management: Download Our White Paper Now Read more »

CPU Drill-Down Feature in Database Health Monitor A powerful capability has arrived in Database Health Monitor, making CPU troubleshooting faster and more intuitive. For years, DBAs relied on two separate views: CPU by Database and CPU by Query. Each provided insight, but there was no direct connection between them. That changes now. The Problem: Lack of Context The CPU by Database report showed which database used the most CPU, but not why. CPU by Query listed top offenders without showing …

CPU Drill-Down Feature in Database Health Monitor Read more »