Amazon CloudWatch is a native AWS monitoring tool for AWS programs. It provides data collection and resource monitoring capabilities.
$0
per canary run
SolarWinds SQL Sentry
Score 10.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…
$0
Free
Pricing
Amazon CloudWatch
SolarWinds SQL Sentry
Editions & Modules
Canaries
$0.0012
per canary run
Logs - Analyze (Logs Insights queries)
$0.005
per GB of data scanned
Over 1,000,000 Metrics
$0.02
per month
Contributor Insights - Matched Log Events
$0.02
per month per one million log events that match the rule
Logs - Store (Archival)
$0.03
per GB
Next 750,000 Metrics
$0.05
per month
Next 240,000 Metrics
$0.10
per month
Alarm - Standard Resolution (60 Sec)
$0.10
per month per alarm metric
First 10,000 Metrics
$0.30
per month
Alarm - High Resolution (10 Sec)
$0.30
per month per alarm metric
Alarm - Composite
$0.50
per month per alarm
Logs - Collect (Data Ingestion)
$0.50
per GB
Contributor Insights
$0.50
per month per rule
Events - Custom
$1.00
per million events
Events - Cross-account
$1.00
per million events
CloudWatch RUM
$1
per 100k events
Dashboard
$3.00
per month per dashboard
CloudWatch Evidently - Events
$5
per 1 million events
CloudWatch Evidently - Analysis Units
$7.50
per 1 million analysis units
Plan Explorer (SQL Server Query Tuning)
$0
Free
SQL Sentry for Azure SQL Database
$161
Per year per database (annual subscription)
SQL Sentry
1,450
Per year per instance (annual subscription)
Offerings
Pricing Offerings
Amazon CloudWatch
SolarWinds SQL Sentry
Free Trial
Yes
Yes
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
Yes
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
With Amazon CloudWatch, there is no up-front commitment or minimum fee; you simply pay for what you use. You will be charged at the end of the month for your usage.
—
More Pricing Information
Community Pulse
Amazon CloudWatch
SolarWinds SQL Sentry
Features
Amazon CloudWatch
SolarWinds SQL Sentry
SQL Performance Monitoring
Comparison of SQL Performance Monitoring features of Product A and Product B
For out business we find that AWS Cloudwatch is good at providing real-time metrics for monitoring and analysing the performance and usage of our platform by customers. It is possible to create custom metrics from log events, such people adding items to a basket, checking out or abandoning their orders.
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.
It provides lot many out of the box dashboard to observe the health and usage of your cloud deployments. Few examples are CPU usage, Disk read/write, Network in/out etc.
It is possible to stream CloudWatch log data to Amazon Elasticsearch to process them almost real time.
If you have setup your code pipeline and wants to see the status, CloudWatch really helps. It can trigger lambda function when certain cloudWatch event happens and lambda can store the data to S3 or Athena which Quicksight can represent.
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.
Memory metrics on EC2 are not available on CloudWatch. Depending on workloads if we need visibility on memory metrics we use Solarwinds Orion with the agent installed. For scalable workloads, this involves customization of images being used.
Visualization out of the box. But this can easily be addressed with other solutions such as Grafana.
By design, this is only used for AWS workloads so depending on your environment cannot be used as an all in one solution for your monitoring.
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
It's excellent at collecting logs. It's easy to set up. The viewing & querying part could be much better, though. The query syntax takes some time to get used to, & the examples are not helpful. Also, while being great, Log Insights requires manual picking of log streams to query across every time.
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
Support is effective, and we were able to get any problems that we couldn't get solved through community discussion forums solved for us by the AWS support team. For example, we were assisted in one instance where we were not sure about the best metrics to use in order to optimize an auto-scaling group on EC2. The support team was able to look at our metrics and give a useful recommendation on which metrics to use.
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).
Grafana is definitely a lot better and flexible in comparison with Amazon CloudWatch for visualisation, as it offers much more options and is versatile. VictoriaMetrics and Prometheus are time-series databases which can do almost everything cloudwatch can do in a better and cheaper way. Integrating Grafana with them will make it more capable Elasticsearch for log retention and querying will surpass cloudwatch log monitoring in both performance and speed
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
