SAP HANA slowdowns are easy to misread when teams start with infrastructure symptoms alone. Learn how wait-based analysis can help database teams identify where delay is building, what changed, and which SQL, blocking, plan, or resource context matters most.
SAP HANA Under Pressure, Part 1: How to Diagnose Slowdowns with Wait-Based Analysis
Why SAP HANA Performance Is an Application Owner Problem, Not Just a DBA Problem
When SAP HANA performance drops, the impact doesn’t stay in the database team. Application owners are often left managing escalations without enough visibility to explain what’s wrong. Here’s why that gap matters and how shared database insight can help.
ITSM for Healthcare: Compliance, Assets, and the Help Desk You Actually Need
Healthcare IT teams operate under a different kind of pressure. They are supporting clinicians, protecting sensitive patient data, managing distributed assets, and keeping critical systems available across hospitals, clinics, labs,…
ITSM for Financial Services: Change Management, Audit Trails, and What Regulators Actually Want
It’s three weeks before your SOX audit. The auditors send their scope letter with a routine request: “Provide a complete population of all production changes to core banking systems for…
When ITSM Meets IT Operations: How Integrated Visibility Reduces MTTR
Resolving incidents has become a team sport. Service desk analysts handle tickets, IT operations teams monitor infrastructure, and application owners monitor performance and user experience. The more complex the stack…
Monitor SAP HANA With SolarWinds Database Performance Analyzer
SolarWinds® Database Performance Analyzer now supports SAP HANA. We look at what this means for teams that need faster, more focused database troubleshooting.
The High-Performance DBA: CPU Under Pressure, Part 2: Troubleshooting SQL Server
This is the second of two connected posts on SQL Server CPU.
In this post, Kevin Kline focuses on the moving parts that turn into real incidents: SQL Server wait statistics, thread scheduling pressure, troubleshooting workflow, and how observability tools shorten the path from symptom to root cause. In Part 1, we looked at how SQL Server uses CPU, why high CPU usage in SQL Server is often misunderstood, and which configuration habits help create a more stable, high-performance environment.
The High-Performance DBA: CPU Under Pressure, Part 1: How SQL Server Uses CPU
This is the first of two connected posts on database performance tuning. In this post, Kevin Kline explains how SQL Server uses CPU, why high SQL Server CPU usage is often misunderstood, and which configuration habits help build a more stable, high-performance environment.
In the second post, we look at SQL Server wait statistics, scheduler pressure, troubleshooting workflow, and how to arrive at root cause faster.
SolarWinds Service Desk System Requirements and Compatibility Matrix
When you shortlist an IT service management (ITSM) solution or tool, one of the first questions from your architects, security reviewers, and procurement team is predictable: “Will this work in our environment without…
SQLPerformance 2.0: The Next Chapter
SQLPerformance is back. This piece explores why the site still matters, what changed during the transition from SentryOne to SolarWinds, and how the site fits into today’s broader database community.
It also looks at the role SQLPerformance can continue to play as database teams face more complexity, more observability demands, and more pressure to move from reactive work to faster, better-informed decisions.