Overall Satisfaction with SQL Sentry
We use SQL Sentry to help us identify performance issues and remediate them quickly. In addition, we use it to alert on blocking and deadlocks.
- I like the way that the graphs on the dashboard can be selected and synchronize to show how each are related.
- The ease at which problematic SQL can be identified by spikes on the dashboard make this tool invaluable to a Performance Engineering team.
- We have a number of installations across different environments and solution lines. The tool needs to be able to switch between them within the tree view instead of needing to connect to a different installation from the file menu
- We receive frequent timeouts when looking at the Top SQL tab on our busiest SQL servers with a lot of history. Something needs to be done on large repositories
AppDynamics strength lies in showing how the tiers of an application are performing. It shows some things that are good at a macro level for SQL, but it lacks the ability to dig into root cause as well as SQL Sentry. Spotlight and Foglight are also good tools in the space. There was an established user base on SQL Sentry that preferred to not switch.
SolarWinds SQL Sentry Feature Ratings
Using SQL Sentry
60 - This is a mix of users from software developers, architects, managers and support staff. We have three distinct platforms within our health and benefits portfolios that all rely heavily on this tool. It is also used by our performance testing team in conjunction with other application monitoring tools to provide the best value.
5 - The support requirements to keep this tool running are extremely low. The minimum required footprint is really just one server depending on the load and number of servers being monitored. Our DevOps team is able to handle this within their team. They perform the initial installation and handle upgrades as well as license expansion.
- Application Performance Tuning/Engineering
- Performance Test Monitoring
- Deadlock analysis
- Blocking Monitoring and Alerting
- We needed to use the tool to provide additional evidence of unauthorized access
- We have used the tool to provide historical evidence of long running backups when our SQL Agent History is purged.
- We are considering of Extracting the Performance data from the tool into our Reporting and Analytics repositories for predictive analytics on server capacity as well as failure.
- Faster root cause analysis during production outages
- Better platform stability when developers proactively look at poor performing queries in lower life cycles.
Evaluating SQL Sentry and Competitors
- Product Features
- Product Usability
- Prior Experience with the Product
- Existing Relationship with the Vendor
- Positive Sales Experience with the Vendor
i have used many other tools in this space(Idera and Quest to name a couple). I felt that the user experience of how the information was presented was far superior to both of those tools. In addition, the time it takes to get the information I need was much shorter with SQL Sentry.
I wouldn't change a thing. Our evaluation process is very thorough. We look at the overall value to our organization through live trials. We will continue to follow this process to land at the best tool that meets our needs. Like many organizations, we constantly look at available technology. As people, products and technology change, we have found this approach to be the best. Today that process keeps us on SQL Sentry.
SQL Sentry Implementation
- Implemented in-house
Change management was minimal - Since the tool does not have an agent to be installed on the monitored system, it becomes painless to upgrade and can be done within normal business hours. We do not need downtime to monitor new servers or perform upgrades. We did learn that some advanced planning is needed due to security management via group policy. The service account running the monitoring service needs to be a local admin on the machines. Our group policy pulls users out of the local administrators group on a regular basis. So we just need to get the account added to the proper security group prior to adding a new target for monitoring. That is not a tool limitation though.
- Firewall Rules in some cases that were blocking WMI
- Group Policy pulling service accounts out of local admin groups
- Putting too many targets into a single installation without the right number of monitoring services.
SQL Sentry Training
- no training
Generally speaking, the tool is easy enough to pick up without training. I'm sure I could have learned some things via training that I needed to research on my own.
Configuring SQL Sentry
I recommend that beginners go with the defaults and learn as you go in most cases. The vendor has outstanding support and technical evangelists that can help you with your particular situation.
No - we have not done any customization to the interface
No - we have not done any custom code
No additional information at this time.
SQL Sentry Support
Pros | Cons |
---|---|
Quick Resolution Good followup Knowledgeable team Problems get solved Kept well informed No escalation required Immediate help available Support understands my problem Support cares about my success Quick Initial Response | None |
Yes - It depends on the situation and the tool. For many enterprise grade products we frequently pay for premium support
We were using the tool to find evidence of unauthorized access to one of our production systems. The number of times the call of interest was made was much lower than we expected. We thought that there was a problem with the tool capturing information and submitted a case. The SQL Sentry team got back to us very quickly and advised us that the tool was capturing and storing everything per its design. We learned that there is a default minimum duration before a call is stored in the SentryOne database.
They explained what we would need to change if we wanted to capture more or all of the calls. They were also very forthcoming in telling us that lowering the number could have negative impacts on the monitoring service.
They explained what we would need to change if we wanted to capture more or all of the calls. They were also very forthcoming in telling us that lowering the number could have negative impacts on the monitoring service.
Using SQL Sentry
Pros | Cons |
---|---|
Like to use Relatively simple Easy to use Technical support not required Well integrated Consistent Quick to learn Convenient Feel confident using Familiar | None |
- It is very easy to spot times when performance issues were occurring
- The "highlighting" of data in multiple graphs within a selection makes it easy to correlate information
- Fixing deadlocks is so much easier using this tool.
- It is sometimes difficult to hover over certain lines in a graph to see the values. (i.e. Memory)
- It is sometimes difficult to see results over long periods of time. We frequently run into SQL Timeouts and no data if our data range is too wide
SQL Sentry Reliability
Integrating SQL Sentry
- None yet
We currently have AppDynamics and New Relic. We have not done any direct integrations, but we do use all three tools together for looking at separate data points.
- App Dynamics
- New Relic
We do not know if this is supported, and we need to do more research.
WE have not used any of these technologies
No advice to give as we have no integrations.
Relationship with SentryOne
I don't get involved on the terms negotiations, but I have not heard anything bad from the team that does.
Nothing other than be a good customer. They are more than willing to help any of their customers regardless of size or purchased license count. Don't make unreasonable or unrealistic requests. Think about how you want your customers to treat you and pay that forward to SQL Sentry. You won't regret it.
Upgrading SQL Sentry
Yes - Nothing unexpected. The upgrades were simple to perform.
- In one case an upgrade was done to fix a known bug
- Some fixes are to address performance.
- Would love to see the client interface function more like SSMS when connecting to sites. (i.e. Allow multiple sites connected at once)
- Would love to see forward and backward compatibility with the Sentry One client