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…
We didn't actually choose to use it at that company because some members of the team were too stuck on their existing monitoring tool. I was disappointed in that decision.
SQL Sentry seemed to answer these scenarios better than competitors:
1."Death by a thousand cuts" - an execution plan now takes 1.2 seconds that used to take .2 seconds to run. The underlying query is run thousands of times per hour and the load on the server has more than …
We used to use DBTuna. DBTuna recorded every query, but did not record server health statistics. I believe Performance Advisor was able to deliver more information about our system, and have lower impact. When I introduced the tool to our CTO and a lot of our programmers, I was …
I selected this tool over SQL Monitor as it provided the all round package, it seemed to dig deeper into the server that SQL Monitor and the interface is so much nicer to use,
Because of previous experience with the tool, we did a short analysis of other tools and chose SQL Sentry Performance Adviser because of price, functionality, support and high expertise.
For our enterprise software, SQL Server has more predictable functionality and tools than the other products we've examined. If we have a question or a problem, it's quite likely someone else has had to deal with the same thing, and it's possible to find help or tips online …
This solution is perfect for a team with a large server count and, at least, moderate experience supporting a SQL Server environment. If the environment is smaller or the team has less experience working with SQL Server performance tuning methodologies, then the tool may be overwhelming for the users.
Microsoft SQL is ubiquitous, while MySQL runs under the hood all over the place. Microsoft SQL is the platform taught in colleges and certification courses and is the one most likely to be used by businesses because it is backed by Microsoft. Its interface is friendly (well, as pleasant as SQL can be) and has been used by so many for so long that resources are freely available if you encounter any issues.
The Top SQL functionality has been extremely useful for identifying poorly performing queries by resource consumption.
The flexibility of creating your own Advisory Conditions has allowed us to integrate our custom internal alerts into a centralized dashboard and alerting platform.
Being able to highlight any chart on the dashboard and then tool-matching that window across all the other charts makes it much easier to correlate the different performance metrics against each other.
Tuning advice: With all the graphs and data available, it's not always easy to determine the best thing to do. I'd like to see SentryOne provide some best practice analysis based on the historical information collected for the server being looked at.
They could add help tips or links to help documents, when you select a graph on the dashboard. Inexperienced users tend to put blinders on and focus on one thing when they see a high counter or something out of the ordinary. It would be very useful to include a link that provides underlying help. The link would provide an explanation of the counter in detail and offer possible explanations as to why the counter is off.
Microsoft SQL Server Enterprise edition has a high cost but is the only edition which supports SQL Always On Availability Groups. It would be nice to include this feature in the Standard version.
Licensing of Microsoft SQL Server is a quite complex matter, it would be good to simplify licensing in the future. For example, per core vs per user CAL licensing, as well as complex licensing scenarios in the Cloud and on Edge locations.
It would be good to include native tools for converting Oracle, DB2, Postgresql and MySQL/MariaDB databases (schema and data) for import into Microsoft SQL Server.
Absolutely. SQL Sentry is an absolute must have for any company with a SQL Server estate. It provides a force multiplier to effectively manage SQL Server, and the feature sets are second to none. The support and expertise at SentryOne is incredible. They are very supportive of both the platform users and helping your business with the product
We understand that the Microsoft SQL Server will continue to advance, offering the same robust and reliable platform while adding new features that enable us, as a software center, to create a superior product. That provides excellent performance while reducing the hardware requirements and the total cost of ownership of our solution.
I accept that the flexibility of the alerting comes at a price. Other than the alerting SQL Sentry's interface is intuitive. Connecting to a new SQL instance, given that all the needed ports are open in your firewalls is straight forward. Reviewing the performance and queries for an instance is available in with a right click. As you dig in new tabs are created to present the detailed data. I find the ability to filter and rollup metrics on a query very helpful in dealing with the "it's running slow". You can easily compare the metrics of run times for the same query to let the user know, it's probably data your doing a billion reads instead of the usual 100 thousand.
SQL Server mostly 'just works' or generates error messages to help you sort out the trouble. You can usually count on the product to get the job done and keep an eye on your potential mistakes. Interaction with other Microsoft products makes operating as a Windows user pretty straight forward. Digging through the multitude of dialogs and wizards can be a pain, but the answer is usually there somewhere.
The system is working perfectly in capturing data, but we do experience issues with SQL Timeout when viewing results in the remote clients. This may be due to the fact that our monitoring service is consuming most of the CPU, and it is the same server that is hosting the SQL Repository. We could probably fix the issue by separating the SQL instance from the monitoring service.
In most cases the pages load very quickly. In our particular case, we need to do some movement of services to separate our monitoring service to separate infrastructure from the repository. When we first started with SQL Sentry on 5 licenses, we did not have any issues. Since we have now grown that to 25, we are experiencing some challenges. We do not believe this to be a tool problem
From their infancy as a smaller company to now as a global player they have always kept focus on prioritising he customer. They know their product and the technology it supports and are easily accessible for both resolving problems with the product all the way to adding value through additional training and assisting with getting return on investment through utilisation of the many features the product provides.
We managed to handle most of our problems by looking into Microsoft's official documentation that has everything explained and almost every function has an example that illustrates in detail how a particular functionality works. Just like PowerShell has the ability to show you an example of how some cmdlet works, that is the case also here, and in my opinion, it is a very good practice and I like it.
Was suggested that we install the process monitors on a dev or qa database server, but we found it more useful to create an IT db server and put it there (along with a few other apps that we use for monitoring).
Other than SQL taking quite a bit of time to actually install there are no problems with installation. Even on hardware that has good performance SQL can still take close to an hour to install a typical server with management and reporting services.
SQL Sentry offers more features and is customize-able to fit our business needs. It has more centralized management and support. The company's technical support is also top notch. It is also worth mentioning that SentryOne Team Blog is an excellent source. One can find lots of valuable troubleshooting skills on the blog site - very educational and informational.
[Microsoft] SQL Server has a much better community and professional support and is overall just a more reliable system with Microsoft behind it. I've used MySQL in the past and SQL Server has just become more comfortable for me and is my go to RDBMS.
We are running 25 instances through a single monitoring service and it is able to keep up. We are finding that this many instances in our environment is about as many as can be handled. We will need to deploy additional monitoring services. Luckily, there is no additional licensing costs to deploy additional monitoring services. For us, it's just an additional Azure VM.
Better customer service as it alerts me automatically to loss of service issues so I can react and either get things fixed before it impacts the customers or to let my management know as soon as possible
It helps me find expensive SQL so our customers get better performance and we make better use of our resources
Increased accuracy - We went from multiple users having different versions of an Excel spreadsheet to a single source of truth for our reporting.
Increased Efficiency - We can now generate reports at any time from a single source rather than multiple users spending their time collating data and generating reports.
Improved Security - Enterprise level security on a dedicated server rather than financial files on multiple laptop hard drives.
