Redgate’s SQL Monitor helps teams looking after SQL servers be more proactive. SQL Monitor enables monitoring environments custom to the user’s SQL server to recognize issues before they impact users. It supports monitoring on-premises and cloud-based servers from a single interface.
N/A
SolarWinds Pingdom
Score 8.7 out of 10
N/A
SolarWinds Pingdom is a website uptime monitoring and alert tool, with additional reporting and Real User Monitoring capabilities. Pingdom is part of SolarWinds’s DevOps package, enabling full-stack monitoring as a service.
$14.95
per month
Pricing
Redgate SQL Monitor
SolarWinds Pingdom
Editions & Modules
No answers on this topic
Synthetic Monitoring
$10
per month
Real User Monitoring
$10
per month
Enterprise
Custom Pricing
Offerings
Pricing Offerings
Redgate SQL Monitor
SolarWinds Pingdom
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
All prices are per server and include one year’s support and upgrades. For clusters, each node requires a license. Virtual machines also require a license. You don't need to buy extra licenses for multiple SQL Server instances on a server.
Redgate SQL Monitor is well suited for database administrators or companies who implement software that relies on SQL servers. It will help them test new changes and ensure this will not impact the performance of their software. It is a last resort for MSPs to use to get to the bottom of an ongoing performance issue with their SQL server.
I believe the scenarios we used it for were quite well covered, from the executive perspective. The downtime alarms worked very well and were easy to setup, uptime monitoring tools were clear and easy to use, even for non-technical people (C-level) and the SLA management tools allowed us to spend less time, and have less friction, with our clients
You can quickly see how your server is performing and which queries are taking the longest
I gives you the feeling that you are in control of your database, that you know what is going on for when they users ring up and tell you that the server is slow
The PagerDuty integration could be a lot better. When you use the PagerDuty integration, it doesn't send any information about which check failed! It just sends a message like "Timeout (> 30s)" -- this isn't very helpful when we have hundreds of checks. We've worked around this by using both the PagerDuty and Slack integrations and having them both post to the same Slack channel. But this means that when an engineer is paged from PagerDuty, they have to go to Slack (or Pingdom) to find the details about the page; it's not available on the page itself.
Recently added features have made Pingdom less intuitive for our requirements. While Pingdom has a broad offering and remains a good value, it is becoming more than we need. Our customer base is becoming more and more global and Pingdom still lacks Asia-Pacific monitoring, which we will need within a year.
Pingdom is easy to use, very intuitive and has a very short learning curve. From the onset, we've been able to jump in and leverage the tool to accomplish our goals for page speed performance and discover the insights we need to make improvements. Its a well-designed tool and makes for a good user experience.
Support responded the same day to my query, as I was setting the product up but couldn't find the setting I needed. This was successfully resolved in a short time frame, so I was pleased with how quickly we were able to get this resolved. I haven't needed to contact support since.
Redgate SQL Monitor is a lot cheaper than SolarWinds Database Performance Analyzer. I prefer the SolarWinds' design and that it offers integration with other SolarWinds products we already use. SolarWinds supports more than SQL servers (Oracle, MySQL, Maria DB, IBM DB2) and the analysis seems to be much better. The Spiceworks SQL Server monitoring is a free tool and is ideal for monitoring small business SQL instances.
PRTG Network Monitor was a far more complicated tool to use and set up albeit it does both Internal and External monitoring. The setup wasn't intuitive and there are too many configuration options to complete to form an alert
Amazon CloudWatch is specific to AWS resources and cannot be easily use outside of the AWS Ecosystem