SQL Sentry review

SQL Sentry is SolarWinds’ performance-monitoring product for Microsoft SQL Server, not a general-purpose monitor for every database in the SolarWinds portfolio. The published pricing description says it supports SQL Server only, with visibility across SSAS, Azure SQL Database, and Azure Synapse SQL Pools. It also says monitoring has been demonstrated across 800+ SQL Server instances; that is not a published account limit.

SolarWinds’ homepage describes a broader database observability offering: monitoring, diagnostics, and performance optimization across on-premises, cloud, and hybrid environments, plus AI-assisted query optimization. It names SQL Server, Oracle, MySQL, PostgreSQL, MongoDB, and Redis, and says the offering has self-hosted and SaaS options. That broader description should not be read as proof that SQL Sentry itself supports all those databases or deployment models.

The pricing information lists a 14-day free trial, but no SQL Sentry price or billing unit. The page says multi-year contracts are billed annually.

SQL Sentry’s clearest fit is SQL Server performance monitoring. The published product description includes visibility across SSAS, Azure SQL Database, and Azure Synapse SQL Pools, so it covers more than a single on-premises SQL Server setup. The pricing material says monitoring has been demonstrated across 800+ instances, a useful indication of scale, though not a guaranteed capacity or plan cap.

SolarWinds’ homepage describes the wider database offering as covering monitoring, diagnostics, and performance optimization, with AI-assisted query rewriting and optimization. Those are portfolio-level claims, not confirmed SQL Sentry-specific features, so buyers should verify what is included in the SQL Sentry quote.

Remote monitoring can work, but placement matters. In one Reddit thread, users disagreed on how strongly to avoid monitoring remote instances. Several recommended keeping the monitoring service close to the SQL Server to reduce latency; one user reported monitoring across a VPN without major problems. Another commenter reported occasional missing dashboard data when the monitoring service was on-premises and the SQL Server was in AWS. That makes network design a practical part of evaluating the product, not a detail to leave until rollout.

The main buying drawback is price opacity. The published pricing information gives no SQL Sentry price, billing unit, or published plan caps. It lists a 14-day trial, and says multi-year contracts are billed annually, but that still leaves teams unable to compare cost per instance or estimate a deployment from public pricing alone. Get a written quote that spells out licensing, renewal terms, and what the trial includes before switching.

SQL Sentry is described as supporting Microsoft SQL Server only. SolarWinds’ homepage names Oracle, MySQL, PostgreSQL, MongoDB, and Redis for its broader database offering, but the published SQL Sentry description does not establish support for those platforms. The 800+ instance figure is described as a demonstrated deployment, not a maximum or an included allowance.

Remote topology also deserves scrutiny. Reddit users report latency-related risk and possible gaps in collected data when the monitoring service is far from its targets; another commenter says a remote setup worked for them. These are user reports, not a product guarantee. The free Plan Explorer mentioned in a separate Reddit thread is a query-plan analysis tool, not evidence that the SQL Sentry monitoring product is free.

SQL Sentry’s price is not published. The pricing details list one SQL Sentry plan, but give no monthly or annual amount and no billing unit. That means there’s no reliable tier-to-tier price jump to calculate—and no basis for comparing its cost with another database monitor without requesting a quote.

The listed plan is for Microsoft SQL Server performance monitoring. It includes visibility across SSAS, Azure SQL Database, and Azure Synapse SQL Pools; the page also demonstrates monitoring across 800+ SQL Server instances. That figure is not stated as a plan limit. A 14-day free trial is listed. No add-ons are listed in the published pricing details.

One billing caveat: the page says multi-year contracts are billed annually, but does not explain the contract terms or connect them to a published SQL Sentry price. Ask for the quote, billing unit, renewal terms, and any add-on costs before switching.

Treat this as a SQL Server monitoring switch, not a migration to a multi-engine tool. The SQL Sentry listing supports Microsoft SQL Server, with visibility across SSAS, Azure SQL Database, and Azure Synapse SQL Pools. SolarWinds’ broader database homepage names other engines, but that does not establish SQL Sentry support for them.

Before moving, confirm which SQL Server versions and related services your deployment needs covered, how monitoring data and alert settings can be transferred, and whether SQL Sentry is self-hosted or SaaS for your quote. Those SQL Sentry-specific migration, export, and deployment details are not published on the vendor's site. The verdict also flags unresolved latency in remote setups, so clarify that risk for your environment before committing.

We weren’t given Reddit reports about why customers leave SQL Sentry, so we can’t attribute switching complaints to users. Get the export and exit terms in writing; don’t assume historical data will move with you.