When an application slows down, the first question is always the same: is it the host, or is it the database? See how one bank’s NOC answered it in minutes, and how unified IT monitoring takes the guesswork out of triage.
Disaster recovery strategy starts with two questions: How much data can you lose, and how quickly must you recover?
In this article and accompanying webinar, Kevin Kline explains how building a resilient database disaster recovery strategy starts with two vital questions: how much data can you lose, and how quickly must you recover? Explore key considerations for RPO, RTO, SQL Server backups, availability groups, and monitoring.
Checkout was slow. Every dashboard said it was fine…
In this fictional incident, Owen Murphy shows how an application owner can turn a vague slowdown into a focused database investigation.
AI is moving quickly, and DBAs need practical context on what’s happening under the hood. This post is an overview of the LLM internals for DBAs covered in the session. In the article, database expert Kevin Kline looks at how large language models work at a practical level.
Database Alerting Best Practices That Cut Alert Fatigue and Help DBAs Respond to What Matters
Most database teams don’t have an alerting problem. They have a trust problem. This post is an overview of the database alerting best practices covered in the session. In the article, database expert Kevin Kline looks at what makes a good alert and how to turn noise into signal. He also covers throttling, digests, escalation paths, and baselines, plus how SolarWinds tools support them. It doesn’t cover everything, so watch the on-demand webinar for the full walkthrough and demos.
Healthy dashboards don’t always tell the whole story. Our Q4 webinars help you uncover hidden database problems, understand what’s causing them, and decide what to do next.
Want to speak to an expert directly?
Database estates keep growing, but DBA headcount rarely keeps pace. Our State of the Database Report shows DBAs now spend most of their week on reactive firefighting across three to five platforms per organization. Burnout is pushing experienced DBAs out of the role.
In this post, Kevin Kline breaks down the habits that let a single DBA scale coverage without adding headcount. These include treating database code as code, shifting SQL quality checks left, and layering in AI-driven anomaly detection.
A fun, detailed walkthrough in SolarWinds Database Performance Analyzer shows exactly how evidence-based root cause analysis turns a vague business complaint into a resolved problem in minutes.
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.
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.
This is the second of two connected posts on SQL Server memory. In Part 1, we looked at how SQL Server uses memory, why “SQL Server takes care of that” stops being enough, and which configuration habits make life easier.
In this post, Kevin Kline focuses on how SQL Server memory issues arise from plan cache bloat, poor queries, and bad memory grants, plus how DBAs troubleshoot them.
This is the first of two connected posts on SQL Server memory management.
In this post, Kevin Kline explains how SQL Server uses memory, why memory becomes a bottleneck, and which configuration habits help create a more stable, high-performance environment. In the second post, we look at plan cache bloat, query patterns, and troubleshooting.
