Komprise is the database development and management solution from the company of the same name in Campbell, California.
N/A
SolarWinds SQL Sentry
Score 9.0 out of 10
N/A
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…
As any other archiving solution, it is very well suited for environments with a large footprint of unstructured data (CIFS / NFS shares for user data) with a large amount of unused/old files and a need to keep those unused files for long term. In our scenario, due to some legal and contractual constraints we need to keep these files for 15 years. Archiving is a good choice to move the unused files to a cheaper storage tier, both on-prem or cloud.
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.
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.
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
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.
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.
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).
We have used Veritas Enterprise Vault in the past, and besides its being a well-known player on the data archiving market, their tool is far more complex to implement, to manage and to keep working. Komprise is very robust and also very easy to implement, as most part of the job is done on Komprise side. The management console is delivered through a public URL as a SaaS platform. You only need to deploy a few VMs for scan/archiving/user access, which they call "Observer VMs." Komprise also doesn't uses Stub files, which is a poor implementation adopted by the competitor for file access. We had a lot of issues in the past with stub files. Komprise has implemented 'bread crumbs', which are CIFS symlinks to the files on the Observer. It is a very good implementation and it works really well.
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.
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
