Skip to content
Home › SQL Comparisons › SQL Sentry vs SolarWinds DPA
Comparison · Database Monitoring

SQL Sentry vs SolarWinds DPA

SQL Sentry and Database Performance Analyzer (DPA) are both SolarWinds products and share the same DBSH subscription licence. SQL Sentry is the deep monitor for the Microsoft data platform (SQL Server, Azure SQL, SSAS and their hosts); DPA is the agentless, wait-time analysis tool for many engines, from SQL Server and PostgreSQL to Oracle, Db2 and SAP HANA.

Last verified October 2026. Versions checked: SQL Sentry 2026.3, SolarWinds DPA 2026.2. Licensing and features change; check the official sources for the latest details.

Quick verdict

Short answer

If everything you run is SQL Server, Azure SQL or SSAS, SQL Sentry is the SolarWinds product built for it: Top SQL with plan history, blocking and deadlock analysis, an Agent job event calendar, TempDB and index views, Always On monitoring, and Windows, VMware or Hyper-V host metrics. If you run several engines, or Oracle, Db2, SAP ASE or SAP HANA, choose DPA, which samples every session once per second and ranks queries by wait time on all of them. Because the same DBSH subscription licence works in either product, a mixed estate can use SQL Sentry for SQL Server and DPA for the rest.

How we know: This comparison is research-based: supported platforms, architecture, retention, alerting and licensing were checked against SolarWinds' official product pages and documentation on 7 October 2026. We have not installed or run either product. Overhead figures are SolarWinds' own statements, not measurements.

SolarWinds sells two database performance products side by side, and they overlap on SQL Server. SolarWinds itself has been privately held since April 2025, when Turn/River Capital completed its acquisition of the company; it continues to operate under the SolarWinds name.

SQL Sentry (SolarWinds SQL Sentry, originally a SentryOne product) monitors the Microsoft data platform. Version 2026.3 (1 September 2026) supports SQL Server 2017 to 2025, Azure SQL Database, Azure SQL Managed Instance, Amazon RDS for SQL Server, SQL Server Analysis Services 2017 to 2025, Windows Server hosts and VMware or Hyper-V hosts. It comes with Plan Explorer, which SolarWinds also offers as a free standalone tool.

Database Performance Analyzer (DPA) is SolarWinds' cross-engine tool built around wait-time analysis; the documentation's current release is 2026.2. It monitors Oracle, SQL Server, MySQL, Percona, MariaDB, PostgreSQL, EDB Postgres, IBM Db2, SAP ASE and SAP HANA, both self-managed and as managed services on AWS, Azure and Google Cloud.

Side by side

AspectSQL SentrySolarWinds DPA
SolarWinds positioning Deep performance monitoring for SQL Server, Azure SQL and SSAS Wait-time and response-time analysis across many database engines
Monitored engines SQL Server, Azure SQL Database and Managed Instance, SSAS; Microsoft APS and Azure SQL Data Warehouse also listed SQL Server, Oracle, MySQL, Percona, MariaDB, PostgreSQL, EDB Postgres, Db2, SAP ASE, SAP HANA
SQL Server versions 2017, 2019, 2022, 2025 2022 and 2025 self-managed (Windows and Linux); 2019 and 2022 on Amazon RDS; 2022 on Google Cloud SQL
Cloud SQL Server targets Azure SQL Database (all tiers), Managed Instance, Amazon RDS for SQL Server, GCP VMs Azure SQL Database, Managed Instance, Amazon RDS, Google Cloud SQL
Host and hypervisor metrics Windows Server, VMware vCenter and Hyper-V hosts (three hosts per licence) VM metrics collected with a DBSH licence when the instance runs on a VM
Collection Agentless polling by a Windows monitoring service; Top SQL from a trace (rowset by default, or Extended Events) Agentless JDBC quickpoll of sessions and waits, once per second by default
Server and repository Monitoring service, client and Portal on Windows; repository on SQL Server 2017 or later DPA server on Windows Server or Linux (x86-64); repository on SQL Server, Oracle, MySQL or Azure SQL Database
Default retention Top SQL, blocking and deadlocks 15 days; dashboard detail 3 days, rolled up for 1 to 3 years Per-second detail 30 days, hourly 90 days, daily 5 years
Licence DBSH subscription per monitored target DBSH or DBSHDS subscription per monitored instance
Main trade-off Deepest SolarWinds coverage of SQL Server, but Microsoft platform only Many engines with one method, but less SQL Server-specific detail

Key differences

How SolarWinds positions each product

SolarWinds presents SQL Sentry as a SQL Server performance monitoring product: its product page lists a performance analysis dashboard, Top SQL, index analysis, deadlock and blocking analysis, TempDB analysis, an event calendar with event chains, storage forecasting, Always On availability group monitoring and SSAS monitoring. DPA is presented as cross-platform database performance analysis, built on wait-time analytics and machine-learning anomaly detection, with table tuning advisors and AI Query Assist.

In practice the split is depth against breadth. SQL Sentry knows more about SQL Server and the Windows and virtualisation layers around it. DPA applies one method, sampling what every session is waiting on, to many engines, which makes it the SolarWinds choice for Oracle, Db2, SAP and open source databases.

SQL Server specifics

  • Waits. DPA records the wait type of every active session every second and charts total wait time per query; that is its core view. SQL Sentry shows waits on its dashboard and, since 2026.3, lets you filter which waits are collected.
  • Top queries and plans. SQL Sentry's Top SQL captures completed batches, procedures and statements above thresholds (default minimum duration five seconds) and keeps a chronology of plan changes that opens in Plan Explorer. DPA ranks queries by wait time and collects plans as part of its analysis.
  • Blocking and deadlocks. Both cover them. SQL Sentry has dedicated Blocking SQL and Deadlocks views; DPA shows blocking sessions and SQL Server deadlock details with victims, survivors, locked resources and victim impact.
  • Query Store. We did not find Query Store integration documented for either product; both rely on their own collection.
  • Availability groups. SQL Sentry has an AlwaysOn view with alerting. DPA shows AG status and annotations and alerts on failover and status change, but not for distributed AGs.
  • Beyond the engine. Only SQL Sentry covers SSAS, SQL Server Agent job scheduling through the Event Calendar, and Windows, VMware and Hyper-V hosts.

Both tools turn snapshots like the one below into history. This T-SQL lists the cached query plans with the highest total elapsed time since they entered the plan cache (times are in microseconds, and the figures disappear when a plan leaves the cache, which is one reason monitoring tools store them):

-- T-SQL (SQL Server, Azure SQL)
SELECT TOP (10)
       qs.execution_count,
       qs.total_elapsed_time / qs.execution_count AS avg_elapsed_us,
       qs.total_worker_time AS total_cpu_us,
       qs.total_logical_reads,
       t.text AS sql_text
FROM sys.dm_exec_query_stats AS qs
CROSS APPLY sys.dm_exec_sql_text(qs.sql_handle) AS t
ORDER BY qs.total_elapsed_time DESC;

For background, see our performance tuning lesson, indexes lesson and the error 1205 deadlock page.

Supported SQL Server versions

This can decide the choice on its own. SQL Sentry 2026.3 lists SQL Server 2017, 2019, 2022 and 2025. DPA's current supported-versions page lists self-managed SQL Server 2022 and 2025 only (on Windows and Linux), with SQL Server 2019 still listed for Amazon RDS. SolarWinds states that DPA drops support for a version once the database vendor does, although monitoring an unsupported version may still work without support. If you run SQL Server 2017 or 2019 on your own servers, SQL Sentry is the documented option of the two.

Architecture and retention

Both are self-hosted and agentless. SQL Sentry runs a monitoring service on Windows (SolarWinds says one service typically handles 50 to 100 targets, and you add services to scale), stores data in a SQL Server 2017 or later database, and offers a Windows client plus a web Portal. DPA is one server application on Windows Server 2022 or 2025 or on Linux, with a repository on SQL Server, Oracle, MySQL or Azure SQL Database. SolarWinds says DPA adds less than 1% overhead to the monitored instance, which is the vendor's figure. DPA Central links several DPA servers.

Default retention differs. SQL Sentry keeps Top SQL, Blocking SQL and deadlock history for 15 days, event history for 30 days, and dashboard metrics at full detail for 3 days before rolling them up, down to daily values kept for a year and coarser intervals kept for up to three years. DPA keeps per-second data for 30 days, hourly summaries for 90 days and daily summaries for five years.

Neither product is SaaS. SolarWinds' SaaS option for databases is SolarWinds Observability SaaS, whose database monitoring covers SQL Server, PostgreSQL, MySQL, Oracle, MongoDB, Redis and others; it is a separate product and is compared with Datadog on Datadog vs SolarWinds DPA.

Alerting

SQL Sentry uses Conditions (including customisable Advisory Conditions) with Actions such as sending email, running a SQL Server Agent job, sending an SNMP trap or writing to the Windows Event Log, and Response Rulesets to control how often an action fires. DPA has wait time, resource, administrative and custom alerts, with email templates, SNMP traps and Platform Connect for ServiceNow and PagerDuty.

Pricing and licensing

Shared licence. SolarWinds' Database Self-Hosted (DBSH) and Database Self-Hosted DBaaS (DBSHDS) licence types are subscription only and, per the DBSH documentation, can be used with either DPA or SQL Sentry. SQL Sentry adopted DBSH in version 2024.4, and DPA in 2024.4 as well. DBSHDS covers database services such as Azure SQL Database.

SQL Sentry. Licensed per monitored target (SQL Server instance, SSAS instance or Azure SQL database). The Portal, clients and monitoring services need no extra licence; the instance that hosts the SQL Sentry database can be monitored with a free licence; and each licence lets you watch three Windows, VMware or Hyper-V hosts. A 14-day trial is available.

DPA. Licensed per monitored database instance. Perpetual licences with annual maintenance were sold for earlier DPA versions, and Category 1 and Category 2 licences appear in the documentation as legacy types. A 14-day trial is available.

SolarWinds does not publish prices for either product; both are quote-based.

Pricing checked on the vendors' official pages on 7 October 2026. Prices change; confirm before buying.

Where each one leads

SQL Sentry strengths

  • Deep SQL Server coverage: Top SQL, plan history, blocking, deadlocks, TempDB, indexes, AlwaysOn
  • Monitors SSAS as well as the Database Engine
  • Event Calendar shows SQL Server Agent jobs and other scheduled events
  • Windows, VMware and Hyper-V host monitoring included with each licence
  • Supports SQL Server 2017 and 2019 on your own servers

SolarWinds DPA strengths

  • One wait-time method across ten engine families, including Oracle, Db2, SAP ASE and SAP HANA
  • Once-per-second sampling with per-second detail kept for 30 days
  • Daily summaries retained for five years by default
  • DPA server can run on Linux as well as Windows
  • Anomaly detection and table tuning advisors

Limitations

SQL Sentry limitations

  • Microsoft platform only
  • Windows-based monitoring service, client and Portal
  • Shorter default retention for Top SQL and blocking data (15 days)
  • No Query Store integration found in the documentation

SolarWinds DPA limitations

  • Self-managed SQL Server support listed only for 2022 and 2025
  • No SSAS, SQL Server Agent calendar or hypervisor host monitoring
  • No Query Store integration found in the documentation
  • Distributed availability groups are not covered by its AG features

When to choose each

Choose SQL Sentry if

  • Your estate is SQL Server, Azure SQL and SSAS only
  • You run SQL Server 2017 or 2019 on your own servers or VMs
  • You want Agent job schedules, host and hypervisor data next to query performance
  • Your DBAs work mainly in Windows tools and want Plan Explorer built in

Choose SolarWinds DPA if

  • You run several engines, especially Oracle, Db2, SAP ASE or SAP HANA
  • Your main need is ranking queries by wait time and response time
  • You want long summarised history for trend reports
  • You prefer a Linux server for the monitoring application

When neither is right

Final recommendation

Bottom line

SolarWinds' own split is sensible: SQL Sentry for SQL Server shops that want depth on the Microsoft platform, including SSAS, Agent jobs and the virtualisation layer; DPA for estates with several engines where wait-time analysis is the common language. Check the SQL Server version lists first, because DPA's current list starts at SQL Server 2022 for self-managed instances. As the DBSH subscription licence works in either product, a mixed estate can run both under one licence type (confirm with SolarWinds how licences are allocated between products on your contract). For other options, see SQL Sentry alternatives and SolarWinds DPA alternatives.

Frequently asked questions

Are SQL Sentry and DPA the same product?

No. Both are sold by SolarWinds, but SQL Sentry focuses on SQL Server, Azure SQL and SSAS, while DPA does wait-time analysis across many engines. They share the DBSH licence type.

Can one licence be used for both?

SolarWinds documents that DBSH and DBSHDS subscription licences can be used with either DPA or SQL Sentry. Ask SolarWinds how moving licences between products works for your contract.

Which one monitors Oracle or PostgreSQL?

DPA. SQL Sentry covers only Microsoft platforms. DPA lists Oracle 19c to 26ai and PostgreSQL 14 to 18, among others.

Do they install agents?

No. SolarWinds documents both as agentless: SQL Sentry polls from its monitoring service, and DPA connects over JDBC and samples sessions once per second.

Is either available as SaaS?

No. Both are self-hosted. SolarWinds' SaaS database monitoring is part of SolarWinds Observability SaaS, a separate product.

Sources

Checked October 2026.

How we research comparisons: our editorial method.

More comparisons

Browse all SQL comparisons or the tools directory.