SQL Diagnostic Manager for Microsoft SQL Server helps database administrators to find and fix Microsoft SQL Server performance problems in physical, virtual, and cloud environments. Unlike its competition, it provides effective scalability, advanced SQL query analysis and optimization, prescriptive analysis with corrective SQL scripts, powerful automated alert responses, broad PowerShell integration, complete customization, and extensive support for current and legacy Microsoft SQL Server and…
$1,996
per instance with first year maintenance included
Splunk Enterprise
Score 8.4 out of 10
N/A
Splunk is software for searching, monitoring, and analyzing machine-generated big data, via a web-style interface. It captures, indexes and correlates real-time data in a searchable repository from which it can generate graphs, reports, alerts, dashboards and visualizations.
SQL Server [Business Intelligence] Manager is useful for tracking performance across SSIS, SSRS and SSA and have the data represented in dashboards. It helps improve performance and helps end users. However, several features are redundant for smaller organization that can use the tools that comes with existing Microsoft products. These features also takes time to learn and use.
It's well suited for what I do, which is network security operations. And that's for anything from troubleshooting incidents, troubleshooting performance, troubleshooting for the purpose of a compliance and auditing. It's not best suited for users who are new in terms of they're new to the product and they have expectations that probably Splunk cannot meet.
SQLdm does a good job of providing information at a high level, but also allows me to drill down to specific queries and events if needed. I don't always need to sift through tons of details to get the information I need. It also gives a very wide range of information from SQL specific metrics, to OS metrics, to VM metrics, all the way up to host server metrics.
I like how the alert and notification system can be customized. For example, if you know a certain server regularly has long-running queries, you can adjust the alert to not fire unless a query has been running for 30 minutes while the rest of the servers fire after 30 seconds. That is very helpful in not being bombarded at dinner with alerts from a server similar to, "I've been at 90% cpu for 26 milliseconds!!!!!!!...and now it's back down to 30%" Good information to know, but not something you need to literally lose sleep over.
I like how you can configure different servers to be monitored differently. For example, you can have a group of servers called DEVELOPMENT that you can turn on heavier monitoring on so you can test how changes in applications might affect the SQL environment, but in the PRODUCTION group, you may only want to enable the heavier analysis and logging when performance issues are actively being reported.
Windows client has some issues. When you have small time intervals for your data collection, it can cause the client to become unresponsive and require you to restart it.
It takes more time to get the web client running than it does to get the windows client running.
The visualizations have been the same for the last eight years--could use a little bit of a refresh.
We are using Splunk extensively in our projects and we have recently upgraded to Splunk version 6.0 which is quite efficient and giving expected results. We keep track of updates and new features Splunk introduces periodically and try to introduce those features in our day to day activities for improvement in our reporting system and other tasks.
You can literally throw in a single word into Splunk and it will pull back all instances of that word across all of your logs for the time span you select (provided you have permission to see that data). We have several users who have taken a few of the free courses from Splunk that are able to pull data out of it everyday with little help at all.
Splunk maintains a well resourced support system that has been consistent since we purchased the product. They help out in a timely manner and provide expert level information as needed. We typically open cases online and communicate when possible via e-mail and are able to resolve most issues with that method.
The online course was simple clear and described the main capabilities of the solution. There is also an initial module that can be done for free so anyone can familiarize themselves with the functionality of this solution. On the other hand, however, there could be more free online courses. Maybe even with a certificate, this would broaden the group of people who are familiar with the platform while increasing familiarity with the solution itself.
IDERA SQL Diagnostic Manager for SQL, Redgate SQL, and MonitorLogicMonitor are similar products to each other. We decided on IDERA SQL Diagnostic Manager for SQL because our experience with locating heavy queries has been very good and it provides real-time monitoring of all servers and databases. It also allows you to have a large volume of historical data which allows you to analyze trends in the databases.
I didn't get to fully evaluate Logstash as our corporation was already using Logstash, but both seemed like viable solutions to the problem that we were having. I wanted to evaluate Logstash some more, both did seem like they would work for the business needs that we had, we went with splunk as many teams were already using it.
I don't have any numbers to share but Splunk has positively served as a 24/7 monitoring tool that has saved hours of work by self-detecting, saving statistics and alerting problems in the system or from external interfaces as soon as they happen.
Splunk dashboards does a solid job in collecting, analyzing data and creating reports that contain an entire day's activity and then automatically sent out to the business.
Splunk is very easy to learn and very useful to any program or business application.
