SQL Sentry review

SQL Sentry is SolarWinds’ performance-monitoring product for Microsoft SQL Server. It belongs in the database operations stack, where teams monitor SQL Server instances and investigate performance issues; it is not presented as a database API, SDK or query library. The SQL Sentry plan includes visibility across SSAS, Azure SQL Database and Azure Synapse SQL Pools, and SolarWinds says monitoring has been demonstrated across more than 800 SQL Server instances.

Reddit users describe a deployment with a monitoring service and a SQL Sentry repository. That points to components whose network placement matters, particularly when monitored instances are remote. SolarWinds’ homepage also describes a broader database observability offering for SQL Server, Oracle, MySQL, PostgreSQL, MongoDB and Redis, with self-hosted and SaaS options. Those are broader SolarWinds database claims; the homepage does not confirm that every engine or deployment option applies to SQL Sentry. Confirm the SQL Sentry architecture and supported deployment model with SolarWinds before designing around it.

SQL Sentry is an operational monitoring tool, not a developer library. The integration surface described for it is monitoring Microsoft SQL Server, with visibility across SSAS, Azure SQL Database and Azure Synapse SQL Pools. The vendor’s homepage does not publish a SQL Sentry REST API, webhooks, CLI, plugins, SDKs or supported programming languages. Confirm API and SDK support, authentication, permissions and integration options in SolarWinds’ product documentation before planning custom automation.

The homepage describes the broader SolarWinds database offering as able to monitor, diagnose and optimize databases, and says SolarWinds AI can rewrite slow queries in one click. It does not establish that those features are included in SQL Sentry. Reddit users discuss Plan Explorer, a free tool for analyzing execution plans, and report that it requires the same SHOWPLAN permissions used for plan analysis. Treat that as a separate query-plan workflow rather than evidence of a SQL Sentry API. For a production design, ask SolarWinds which SQL Sentry features and integrations are available in your specific deployment.

SolarWinds lists a 14-day free trial for SQL Sentry, but no free plan. The SQL Sentry plan is for Microsoft SQL Server performance monitoring and includes visibility across SSAS, Azure SQL Database and Azure Synapse SQL Pools. The pricing page does not publish a price or billing unit, so we cannot estimate a per-instance, per-server or subscription cost from the published figures.

The pricing page says multi-year contracts are billed annually. It does not publish how the bill changes with monitored instances, seats, data volume or deployment size, or list overage rates and add-ons. SolarWinds says monitoring has been demonstrated across 800+ SQL Server instances; that is a scale example, not a stated product limit or price tier. Ask for a quote tied to your instance count, Azure services, contract term and deployment topology. Include the cost of operating the monitoring service and repository in your infrastructure estimate, especially if your monitored instances span networks or cloud regions.

SolarWinds does not identify SQL Sentry as open source or publish a source license for it. Treat it as a vendor product, not a component you can freely modify or self-host from an open-source repository. The broader SolarWinds database offering lists self-hosted and SaaS deployment options, but the homepage does not confirm which apply to SQL Sentry specifically.

Reddit users describe a SQL Sentry repository and monitoring service, so ask SolarWinds what you operate, where its data is stored and what export options are available. The vendor does not publish SQL Sentry data-export or migration details on its homepage. Before rollout, confirm whether you can export collected metrics, alerts and configuration in usable formats, and what happens to historical data when you end a contract. Those answers determine how much effort it would take to move monitoring workflows to another product.

Network placement is the clearest production consideration raised by users. In one Reddit thread, commenters recommend keeping the monitoring service close to monitored SQL Server instances to reduce latency; one says remote monitoring worked across a VPN, while another reports sporadic missing data during network issues. A separate commenter warns that cross-site bandwidth can also matter. These are user reports, not vendor guarantees, so test the actual route and failure behavior in your environment.

SolarWinds says monitoring has been demonstrated across 800+ SQL Server instances, but does not present that as a limit or reliability commitment. Before depending on SQL Sentry, confirm supported deployment topology, recovery behavior, data retention, security controls and applicable compliance documentation with the vendor. Also validate permissions for the monitoring and query-plan tasks you need. Reddit sentiment is mixed: some commenters praise Plan Explorer’s query-plan views, while another thread opens with a report of slow performance and issues.