SolarWinds Database Performance Analyzer now supports SAP HANA, expanding the SolarWinds database portfolio for SAP Basis teams, DBAs, and IT operations teams that need a stronger way to investigate slowdowns with wait-based analysis. For teams evaluating the SolarWinds database portfolio, this means they can move beyond infrastructure symptoms and see wait time, SQL activity, execution plans, blocking conditions, and resource trends in one workflow.
“Move beyond infrastructure symptoms and into the database layer.”
Why this launch matters
That matters because SAP HANA supports some of the most business-critical workloads in the enterprise, including ERP, analytics, and other transaction-heavy processes where delays show up fast to end users. The DPA 2026.2 announcement on THWACK highlights this launch in the context of broader database troubleshooting needs. When teams hear that SAP is slow, the first signal often comes from outside the database in the form of rising CPU pressure, memory, or disk activity. But those symptoms do not explain whether the root cause is inefficient SQL, memory pressure, blocking, or a change in execution plan behavior.
“When SAP slows down, teams need evidence, not guesswork.”
Move beyond infrastructure symptoms
This is where DPA changes the troubleshooting motion. Instead of stopping at infrastructure charts, it extends wait-based analytics into the database layer for SAP HANA and helps teams understand what is slowing down, why it is slowing down, and where to focus first. In practice, that means teams can review rising wait time, identify the SQL statements involved, inspect execution plans, and correlate the slowdown with database resource activity from the same dashboard.
“Wait-based analysis helps teams find the cause, not just the symptom.”
Correlate waits, memory, and SQL behavior
The SolarWinds database portfolio becomes especially valuable here because SAP HANA is an in-memory platform where memory pressure can become critical quickly. DPA tracks CPU usage, HANA memory consumption, disk usage, active connections, and related workload behavior on the same timeline as wait events and SQL statement performance. That context helps teams decide whether the issue is broad capacity pressure, a localized query problem, or a workload pattern that needs tuning.
“In SAP HANA, memory context matters as much as raw activity.”
Watch for plan drift before performance gets worse
Execution plan visibility is another reason this launch matters. Queries that performed well before can become much slower and more resource-intensive after data distribution changes, table growth, or optimizer decisions shift the execution path. DPA helps teams compare plan behavior and identify plan changes that coincide with rising wait time, making it easier to investigate plan drift before it turns into a larger performance problem.
“A familiar query can still become a different performance problem.”
Support multi-database environments and migration work
In multi-database environments, the SolarWinds database portfolio also helps standardize troubleshooting across platforms. DPA already applies the same wait-based approach across other supported databases, and SAP HANA now joins that broader monitoring model. For organizations running SAP HANA alongside Oracle, SQL Server, PostgreSQL, MySQL, or other database platforms, that consistency can reduce operational friction and make cross-platform diagnosis more repeatable.
“One troubleshooting approach helps reduce friction across database platforms.”
The SolarWinds database portfolio is also useful during migration and modernization efforts because teams can establish baselines before change and compare behavior after cutover. DPA supports SAP HANA Platform and Express Editions version 2.0 and higher, SAP HANA Cloud version 2026.2 and higher, and both single-container and multi-container architectures. That gives teams one monitoring workflow across on-premises and supported cloud deployments while they validate whether migration and tuning decisions are improving performance. For version-specific support details, see the DPA 2026.2 release notes.
“Better baselines make migration decisions easier to validate.”
Keep monitoring overhead low
Operationally, DPA keeps monitoring overhead low. DPA is agentless, uses read-only monitoring credentials, and typically adds less than 1% overhead on the production database server. For DBAs and governance teams, that reduces rollout friction because there is no agent software to manage on the SAP HANA host and no need to grant broad administrative access just to monitor performance.
From a day-to-day workflow perspective, teams can start on the DPA home page, identify instances with high wait times, and drill into waits, SQL statements, plans, blocking, and related metrics from there. That structured investigation path helps teams spend less time arguing about where to begin and more time working from evidence.
Why this matters to your business
With SAP HANA now included, the SolarWinds database portfolio gives teams a clearer path from symptom to root cause. Instead of treating CPU saturation, memory pressure, or slow SAP transactions as the end of the story, teams can use those signals as the start of a deeper database investigation grounded in waits, workload behavior, and execution context.
The financial impact goes beyond avoiding unnecessary hardware purchases. Optimizing workloads can help teams make better use of the infrastructure they already have, but time is money as well. Slow queries can slow business processes, delay information flow, and slow decision-making across the company. The longer performance issues persist, the more those downstream business costs add up.
FAQ
What does it mean that SolarWinds DPA now supports SAP HANA?
SolarWinds Database Performance Analyzer can now monitor SAP HANA using the same wait-based approach it uses for other supported database platforms. As a result, SAP Basis teams, DBAs, and IT operations teams get a stronger way to investigate slowdowns at the database layer.
What can teams see with SAP HANA monitoring in DPA?
From one interface, teams can review wait time, SQL activity, execution plans, blocking conditions, memory usage, CPU, disk activity, and connection trends. This makes it easier to move from a general symptom to a focused diagnosis.
Why is wait-based analysis useful for SAP HANA?
Wait-based analysis shows why work is slowing down, not just that something is under pressure. Instead of relying on infrastructure charts alone, teams can look at waits, SQL behavior, execution plans, blocking details, and workload context together.
Can DPA monitor SAP HANA in both on-premises and cloud environments?
Yes. DPA supports SAP HANA Platform and Express Editions version 2.0 and higher, SAP HANA Cloud version 2026.2 and higher, and both single-container and multi-container architectures. Teams can monitor SAP HANA on-premises and in SAP HANA Cloud, with AWS Cloud support coming soon.
Does SAP HANA monitoring in DPA require an agent on the database server?
No. DPA is agentless, so there is no software to install on the SAP HANA database server or the underlying Linux operating system. Teams provide the hostname or IP address, port, database name, and read-only monitoring credentials, and DPA validates the connection and starts collecting data.
More Resources
- SAP HANA Monitoring
- SolarWinds database portfolio
- DPA 2026.2 announcement on THWACK
- DPA 2026.2 release notes
- The High-Performance DBA: CPU Under Pressure, Part 1
