SolarWinds SQL Sentry

SolarWinds SQL Sentry

Top Rated
About TrustRadius Scoring
Score 8.8 out of 100
Top Rated
SolarWinds SQL Sentry

Overview

Recent Reviews

SentryOne review

8 out of 10
November 10, 2021
We use it to monitor our critical SQL server cluster and it is currently just used by the DBAs. It allows us to monitor in real time but …
Continue reading

SQL Sentry makes my job easier

10 out of 10
April 21, 2021
We use SentryOne to monitor our Production SQL instances for the entire organization. We choose SentryOne as our monitoring solution to …
Continue reading

SQL Sentry Review

10 out of 10
June 25, 2020
We use SQL Sentry to monitor and alert on our SQL Server Environment. It helps us troubleshoot live issues as they occur using the …
Continue reading

Reviewer Sentiment

N/A
Positive ()
N/A
Negative ()
Learn how we calculate reviewer sentiment

Awards

TrustRadius Award Top Rated 2022
TrustRadius Award Top Rated 2021
TrustRadius Best of Award, Best Of Customer Support 2021
TrustRadius Award Top Rated 2020

Popular Features

View all 5 features

Performance dashboard (101)

8.9
89%

Top SQL (101)

8.5
85%

Intelligent alerting (95)

8.2
82%

Historical trend data (99)

8.0
80%

Reviewer Pros & Cons

View all pros & cons

Video Reviews

Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of SolarWinds SQL Sentry, and make your voice heard!

Pricing

View all pricing

Plan Explorer (SQL Server Query Tuning)

$0

On Premise
Free

SQL Sentry for Azure SQL Database

$161

On Premise
Per year per database (annual subscription)

SQL Sentry

1,450

On Premise
Per year per instance (annual subscription)

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visithttp://www.sqlsentry.com/portal/store

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting / Integration Services

Features Scorecard

SQL Performance Monitoring

8.1
81%

Product Details

What is SolarWinds SQL Sentry?

SolarWinds SQL Sentry is designed to help data professionals optimize SQL Server database performance in physical, virtual, and cloud environments. SQL Sentry delivers metrics to help users find and fix database performance problems and provides scalability, boasting demonstrated success monitoring 800+ SQL Server instances with one monitoring database.

With SQL Sentry, the user can monitor:

  • SQL Server
  • Azure SQL Database
  • SQL Server Analysis Services (SSAS)
  • SQL Server on Hyper-V or VMware VMs (including host)
  • SQL Server on Azure SQL Database Managed Instance
  • SQL Server on Amazon RDS
  • SQL Server on Amazon EC2
  • SQL Server on Linux

Although a SQL Sentry license can be used to monitor Azure SQL Database in a hybrid environment, dedicated licensing is available for large Azure SQL Database environments.

SolarWinds SQL Sentry Features

SQL Performance Monitoring Features

  • Supported: Performance dashboard
  • Supported: Intelligent alerting
  • Supported: Top SQL
  • Supported: Historical trend data
  • Supported: Virtualization support

Additional Features

  • Supported: Query plan analysis
  • Supported: Blocking and deadlock analysis
  • Supported: Event Calendar
  • Supported: Advisory Conditions
  • Supported: AlwaysOn Availability Groups monitoring
  • Supported: Index analysis
  • Supported: Storage Forecasting
  • Supported: SQL Sentry Portal (installed SQL Sentry web interface)
  • Supported: Environment Health Overview
  • Supported: Tempdb analysis
  • Supported: SQL Server Analysis Services (SSAS) monitoring

SolarWinds SQL Sentry Screenshots

SQL Sentry BlockingSQL Sentry DeadlocksSQL Sentry Index AnalysisSQL Sentry Top SQLSQL Sentry Performance Analysis Dashboard

SolarWinds SQL Sentry Downloadables

SolarWinds SQL Sentry Integrations

SolarWinds SQL Sentry Competitors

  • Redgate
  • Idera
  • Quest

SolarWinds SQL Sentry Technical Details

Deployment TypesOn-premise
Operating SystemsWindows
Mobile ApplicationNo

Comparisons

View all alternatives

Reviews

(1-25 of 98)
Companies can't remove reviews or game the system. Here's why
Score 9 out of 10
Vetted Review
Verified User
Review Source
We had a use case several weeks ago where our SQL Server slowed down and the waiting tasks in the activity monitor ramped up to the thousands. The server wasn't down literally, but it felt like it as all of the applications were waiting to get their response from the SQL Server. Once we logged into [SolarWinds] SQL Sentry, we were able to track down what was the root cause and identify a rouge query that was overloading the server and causing locks for several tables.
Score 8 out of 10
Vetted Review
Verified User
Review Source
There was one blocker when [the] client was facing the slowness issue while adding the cart item. SQL Sentry helps to identify the scenario and long running query. It's difficult to monitor 24/7 the same manually but SQL Sentry helped to do that in order to understand the problem. Further, the suggestions and warnings were also helpful.
Score 9 out of 10
Vetted Review
Verified User
Review Source
Our users got accustomed to having to log out every half hour from our principal application because of a cyclical performance issue. We were unaware of the performance issue as we weren't logged in as long as they were, only logging in to check on a data point or behavior of a controller before logging out again. After we got SQL Sentry, we were able to view a cyclical performance issue that consumed more memory than was needed for what was a simple and small result set returned. With the cycle identified, we were able to find the offending procedure and improve performance. Our users no longer were disrupted every 30 minutes and could instead use the application.
November 10, 2021

SentryOne review

Score 8 out of 10
Vetted Review
Verified User
Review Source
IO waits were high and we didn't know why but using SentryOne we established IO performance on the storage was reduced which then helped us identify a problem with one of our storage controllers. Without SentryOne it would have been impossible to show the storage team evidence of the issue.
Score 9 out of 10
Vetted Review
Verified User
Review Source
We had an overnight interface that had been running longer and longer for no obvious reason. It was difficult to track down because no one was working in the late hours to see what was happening. Using the historical information stored and presented by SQL Sentry, we were able to see an unrelated job was running especially long due to a bad query plan and was negatively impacting the server performance as a whole.
Score 10 out of 10
Vetted Review
Verified User
Review Source
Looking at the dashboard we could see that a server was running consistently at 80+% CPU and spiking to 100% for a few minutes multiple times per day. Using the Top SQL sorted by CPU we were able to identify a single query that was consuming over 90% of total CPU consumption. After turning that query the overall CPU load on the system dropped by 40%.
Score 10 out of 10
Vetted Review
Verified User
Review Source
Fairly recently we had a performance issue with a SQL Server consuming 100% CPU, with the performance advisor we was able to pin point the specific queries that were a problem and advise the vendor. Which lead the vendor to make recommendations and changes to their tables and jobs. This resolved the performance issue.
Score 10 out of 10
Vetted Review
Verified User
Review Source
SQL Sentry monitors the entire server, so when it noticed an issue with high CPU and memory exhaustion, we knew how to configure the server to address both SQL performance and the other processes on the server that needed these resources. Adding resources without allocating them correctly would not have addressed the issue effectively. Knowing the other processes needed more CPU prompted us to use max dop to limit parallelism to not use all cores available.
Mark Lessard | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User
Review Source
A common experience is the SQL optimizer choosing to use a loop join on a large join. We see this even after stats update with full-scan on the associated tables. We have tried the optimizer trace flag.

Process.
Find the SQL statement in Top SQL
Look at the historical run times/plans grid. Notice run time and color of dot. High run-time and different color, you have a bad plan.
Open the plan to review operators
Add hash join query option or join hints. I know this is not best practices according to MS, but the trade-offs in our OLAP environment make it the best choice.


Score 9 out of 10
Vetted Review
Verified User
Review Source
We had a major slow-down on one of our SQL server instances. Users were calling and complaining about time-out errors. With SQL Sentry we could see what the blocking process was, and a bit more information about it than what you get with the Activity Monitor. We were able to kill the blocking process after some assessment and performance improved.
Score 9 out of 10
Vetted Review
Verified User
Review Source
We had an issue where SQL Sentry helped us identify a top slow performing query and what was causing it run slow. After we found this query SQL Sentry gave us some hints and direction as to what we would need to do to fix this problem. We used this data to then fix the problem and saw the performance improve over the next few days.
Score 10 out of 10
Vetted Review
Verified User
Review Source
We have had an issue with blocking, and with SQL Sentry we get an accurate picture of the point in time to see exactly what is happening on the SQL instance. Before, we were dependent on only using wait times for analysis.
June 25, 2020

SQL Sentry Review

Score 10 out of 10
Vetted Review
Verified User
Review Source
We used SQL Sentry to help us identify queries that were causing CPU pressure on our system. Using the Top SQL and sorting by CPU allowed us to quickly zero in the queries that were consuming the most CPU. We were able to make adjustments to alleviate the CPU pressure.
Kevin Dickover, PMP | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
We had a job that ran overnight that started to go long and sometimes fail. PA history showed blocks and bad execution plans that allowed us to look for ways to correct the job. Eventually we rewrote the job so that the parallel executions that were causing the job to fail were eliminated.
Adrian Sullivan | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Reseller
Review Source
When troubleshooting performance issues on a SQL server we exhausted our normal tuning methods. We turned to SQL Sentry and found from monitoring data that this server was seeing a very high amount of Context Switches. This information pointed us to SQL server MAXDOP settings and VM CPU configuration issues. We would not have been able to find this information easily without using SQL Sentry to find the root cause.
Jian Fu | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Review Source
We had a lot of situations where SQL Sentry came to rescue us. One of these situations was when we had a query running slow some times, and the majority of the it worked fast. SQL Sentry caught the execution statement and execution plan for us. After analysing the execution plan and parameter values, we found that the cached plan was not optimsed for a certain parameter values set. With this info, we deployed a plan guide to recompile this query, and then now it runs fast all the time.
Score 8 out of 10
Vetted Review
Verified User
Review Source
Event manager has helped solve multiple issues, both firing alert on real time events and allowing us to troubleshoot issues after the event, gather more details and obtianing proof the issue is resolved when using it with dev / prod. The inital review when simply turning it on highlights some bad configuration settings you may have as well
Derek Knutsen | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Review Source
We were seeing regular spikes in CPU on our production environment. SQL Sentry identified these are coming from a Java process. The queries looked like a report without any criteria set. By sending the graphs and the sources of the queries, our report writers found that a test report was running against our production environment.
May 01, 2020

Force Multiplier

Score 10 out of 10
Vetted Review
Verified User
Review Source
A business intelligence application would intermittently take two to three times its normal duration to complete its processing run, causing significant business disruption. The workload was spread across multiple SQL instances and was a black box from a code perspective. SQL Sentry identified that the application was running multiple processing runs in parallel, but this wasn't visible from a customer perspective, as they only scheduled the run once.
Score 10 out of 10
Vetted Review
Verified User
Review Source
We installed SQL Sentry on a system where performance testing identified poor performance. On the first day, we identified three deadlocks that were the root cause of the performance issue. This was a few days before a very large and critical production release. The deadlocks were fixed and we doubled the number of concurrent users that the application could support.