SolarWinds Database Performance Analyzer vs. Redgate SQL Monitor

A Detailed Comparison for DBAs and Developers

When you’re responsible for keeping databases fast and reliable, two tools come up often: SolarWinds Database Performance Analyzer (DPA) and Redgate SQL Monitor. Both are strong choices, but they take different approaches. This guide combines features, pros/cons, execution plans, drill-down workflows, dashboards, alerting, authentication, and deployment models so you can decide which is the better fit.

---

What Each Tool Excels At

• SolarWinds DPA: Cross-platform, wait-time analysis across SQL Server, Oracle, PostgreSQL, MySQL, Db2, and cloud platforms (Azure, AWS). It shines when you need to explain “why it was slow” at the query level across many engines.
• Redgate SQL Monitor: SQL Server–focused operational monitoring with estate-wide dashboards, blocking/deadlock triage, and developer-friendly query insights. Best for SQL Server and Azure estates where daily operational visibility is critical.

---

Feature Comparison

Area	SolarWinds DPA	Redgate SQL Monitor
Architecture	Agentless, web-based. Collector polls databases, stores data in a repository DB. Very low overhead (<1%).	Base Monitor Windows service + web UI. Repository in SQL Server or PostgreSQL. No agents, uses WMI/SSH.
Database Coverage	SQL Server, Azure SQL DB, Azure MI, Oracle, PostgreSQL, MySQL, MariaDB, Db2, SAP ASE, RDS & Aurora.	SQL Server, Azure SQL DB, Azure MI, Amazon RDS SQL Server. Also supports PostgreSQL, Oracle, MySQL, MongoDB (lighter feature set).
Performance Model	Wait-based response time analysis. Surfaces bottlenecks by wait type per query, user, app, or DB.	Operational + query monitoring. Top Queries, waits, jobs, AG dashboards, and estate-wide health.
Execution Plans	Found in Top SQL Statements → Plans tab. Shows historical plan changes, correlates waits to operators. Advisors suggest indexes, stats updates, or query rewrites.	Found in Top Queries. SSMS-style graphical plans with operator cost %, row estimates vs actuals. Includes plan regression alerts and Code Analysis for anti-patterns.
Blocking & Deadlocks	Blocking chain analysis and deadlock investigation with wait impact metrics.	Extended Events deadlock graphs, blocking chain view, head-blocker identification, real-time blocking alerts.
Alerting	Configured in the web UI. Alerts on waits, query response times, blocking, and deadlocks. VM Option license adds hypervisor-level VM metrics (CPU ready, co-stop, memory contention).	Large library of built-in alerts (CPU, jobs, long queries, backups, blocking, deadlocks). VM utilization included by default via WMI/SSH. Alerts can route to email, Slack, Teams, PagerDuty, or webhooks.
Authentication	Supports SQL logins, Windows authentication, and Azure AD/cloud credentials.	Base Monitor typically runs under a Windows service account with sysadmin/monitoring permissions. Can also use SQL logins.
Deployment	Works on-prem, in VMs, or cloud (Azure SQL, MI, RDS, Aurora). VM metrics require the VM Option license. Best for hybrid/mixed estates.	Works on-prem, in VMs, and in cloud environments. VM metrics collected without an add-on. Optimized for SQL Server/Azure.
Drill-Down Analysis	Instance → Query → Waits → Plan → Advisor. Waits mapped to plan operators for root cause. Deadlocks show blocking session history.	Dashboard/Alert → Server Overview → Top Queries → Plan/Code Analysis. Blocking alerts expand into blocking chains; deadlocks into visual graphs.
Reporting & Dashboards	Live dashboards for waits, resources, and query stats. Build custom reports in the web UI. Reports can be exported, emailed, or scheduled.	Estate dashboards cover health, backups, patching, and capacity across servers. Reports and alerts can be customized, viewed live, or scheduled.
Licensing	Licensed per monitored instance. VM Option license needed for hypervisor metrics.	Licensed per monitored server. VM metrics included in base license.

---

Execution Plan Review & Recommendations

SolarWinds DPA

• Execution plans appear under Top SQL Statements → Plans tab.
• Correlates wait times directly to operators in the plan.
• Tracks plan changes over time to spot regressions.
• Query/ Table Advisors recommend index creation/removal, statistics updates, or query rewrites.

Redgate SQL Monitor

• Plans viewed under Top Queries with a familiar SSMS-style interface.
• Shows estimated vs. actual row counts and operator costs.
• Code Analysis highlights issues like SELECT * or implicit conversions.
• Alerts can fire when a new execution plan causes degraded performance.

---

Drill-Down Workflows

• SolarWinds DPA: Starts from performance forensics → drill from instance waits → specific query → wait types → execution plan → tuning advisors.
• Redgate SQL Monitor: Starts from alerts/operations → drill from dashboard spike/alert → server → top queries → plan/code checks.

Both allow you to move from high-level symptoms down to the exact query/operator at fault.

---

Reporting & Dashboards

SolarWinds DPA

• Live dashboards for wait-time trends, resource metrics, and top queries.
• Build custom reports for tuning, resource usage, or query activity.
• Schedule email or export reports for stakeholders.

Redgate SQL Monitor

• Estate dashboards provide a global view of backups, jobs, AGs, and capacity.
• Reports are customizable and can be viewed interactively or scheduled.
• Alerts feed directly into dashboards and can be exported or pushed to collaboration tools.

---

Pros and Cons

SolarWinds DPA

Pros

• Wait-based analysis pinpoints why queries slow down.
• Multi-platform support (SQL Server, Oracle, PostgreSQL, MySQL, Db2, cloud).
• Agentless, lightweight architecture.
• Advisors provide prescriptive tuning steps.

Cons

• VM metrics require a separate add-on license.
• Less integrated with SQL Server–specific tooling compared to Redgate.
• Focuses more on performance than day-to-day operations.

Redgate SQL Monitor

Pros

• Comprehensive SQL Server/Azure operational coverage.
• Estate dashboards simplify multi-server management.
• Excellent deadlock and blocking visualization.
• Developer-friendly execution plan viewer and Code Analysis.
• VM metrics included by default.

Cons

• Multi-platform support exists but is lighter than for SQL Server.
• Requires a Base Monitor service and repository DB.
• Cannot kill sessions directly from the UI.

---

Practical Examples

1. Query slowed down last week
   • DPA: Drill instance → query → wait types → plan history → apply advisor recommendation.
   • SQL Monitor: Drill alert/dashboard → query → plan viewer → review Code Analysis hints or plan regression.
2. Users report timeouts right now
   • DPA: Open blocking/deadlock view to see waits and blocking chains.
   • SQL Monitor: Check blocking alert, view chain and deadlock graph, and identify the head blocker query.
3. Health and capacity checks
   • DPA: Create a custom report on waits and query performance.
   • SQL Monitor: Review estate dashboards for backups, patches, job failures, and capacity trends.

---

Bottom Line

• Choose SolarWinds DPA if you want:
  • Consistent cross-platform coverage for SQL Server, Oracle, PostgreSQL, MySQL, Db2, and cloud platforms.
  • A wait-based performance lens that explains why queries slow down across different engines.
  • Built-in query and table tuning advisors with prescriptive recommendations.
• Choose Redgate SQL Monitor if you want:
  • SQL Server/Azure–centric daily operations monitoring with unmatched depth (Availability Groups, backups, jobs, blocking/deadlock triage).
  • Estate-wide health reporting and customizable alerting with live dashboards.
  • Ability to also monitor PostgreSQL, Oracle, MySQL, and MongoDB, though coverage for those platforms is not as feature-rich as for SQL Server.
  • Developer-friendly execution plan insights, Code Analysis, and VM utilization included without add-ons.

---

✅ In short:

• For multi-engine estates where consistency across platforms matters most → go with SolarWinds DPA.
• For SQL Server–centric estates (on-prem or cloud) that may also include some PostgreSQL, Oracle, or MySQL → go with Redgate SQL Monitor, since SQL Server coverage is the deepest, and other platforms are supported with lighter features.