IDERA SQL Diagnostic Manager for SQL Server vs. SolarWinds Database Performance Analyzer

If you have several SQL servers and don't have a lot of time or resources to constantly monitor them, SQLdm will be very helpful. For one or two servers, it might be overkill. All of our servers are virtual, so having a tool that can monitor host metrics as well as guest metrics is a plus as well.

Incentivized

I believe that SolarWinds Database Performance Analyzer is a great choice for an organization that does not have a specific DBA or one that is still growing into the role. SolarWinds Database Performance Analyzer is filled with hints, tips, and explanations of the various readings and metrics. This is very useful to help understand what is happening and why, what it means, and what some potential solutions are towards remediating any issues. This is extremely valuable for our development team, allowing them to be more proactive with the queries they write in viewing how they perform and where bottlenecks might be.

Incentivized

• SQL Server Monitoring
• Alerts
• Diagnostics

Incentivized

• Ability to drill down to wait for the issue and have a clear path as to what may be causing the issue.
• Ability to quickly add a new target and the ease of installation and upgrades.
• Reporting features to group my most troublesome customers into a daily report in one email.
• Excellent customer support on any issues I can't immediately solve.

Incentivized

• While there is reporting present in the app, I don't find it to be very configurable. I eventually pointed our reporting software at the SQLdm database so I could craft my own reporting. The reporting that's there is sufficient for a lot of things, but for more detailed analysis and trending, it's a little light
• The config right out of the box feels a little heavy to me. It leans towards the side of over monitoring and over notifying. For example, I view "critical" alerts as those that I'd want to be woken up at 3am for. After a fresh install, I felt like I was getting so many "critical" alerts that I was starting to ignore them. I had to spend a good bit of time tweaking.
• Sometimes the interface seems laggy. Switching between individual servers and switching screens can take what feels like a long time. I'm not sure if it's the way I have the client configured or something up with my machine, but this app in particular feels slower than it should.

Incentivized

• Resiliency of the Monitoring checks after the server underwent maintenance reboot. My experience is the monitor (Action) needs to be started manually. If possible it can automatically detect service/server then start to monitor again when system is back up.
• Much lighter UI.
• Granularity up to minutes.

Incentivized

We have relied on this product for a very long time and it continues to exceed expectations. The product is a vital part of our organization at this point, it would not be very ideal for us to abandon it. We use it almost every day and depend on its alerts for critical parts of our business

Incentivized

I don't want to think about managing clusters of SQL servers in the future without this tool. We have demoed other tools and SolarWinds Database Performance Analyzer is the gold standard for usability and insight into what your servers are doing. The UI is a bit dated, but everything is laid out in a logical manner and drilling down into queries or timeslices is extremely intuitive.

Incentivized

I have had to use their support on a few occasions, for reasons that I am not clear about until recently I have always had problems upgrading the software (although the last 2 updates have gone without issue which I am very pleased to say). On those unfortunate occasions, the support has been brilliant with either excellently documented guides on how to resolve the issue by myself or have been hands-on with calls and screen sharing to remotely fix the issue. Every time the problem was sorted and more importantly, nothing was lost (apart from a bit of time). And as I stated above whatever the problem was that was causing my upgrade issues appears to have been resolved in the last 2 updates.

Incentivized

Follow the guidelines for the capacity of the servers. We found that the DPA databases were getting rather large and also that there are ways to reduce their size built into some of the options.

Incentivized

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.

Incentivized

I have used Spotlight (for Oracle on RAC) but it has been several years. The dashboard was crisp, clean, and intuitive, but the tool had a significant overhead. However, no competitor made a tool that met our needs at the time. I have also used Idera's SQL Diagnostic Manager in more than one company. That tool is helpful for a larger environment than we currently have. But I think it is better at alerting than DPA but worse at just about everything else. The good thing is you can flag an alert as acknowledged, so you stop getting emails. The bad thing is I don't think I could use it to troubleshoot issues like I do with DPA. I do not have enough experience to provide helpful feedback on the others selected.

Incentivized

• Quickly identify issues around deadlocks and blocking. Quickly allowing for resolution
• Quickly and easily enable automation around issues so we can reduce the amount of time it takes for resolution of issues
• Having built-in tools to view things such as index fragmentation--allows you to quickly find correlations in performance issues

Incentivized

• Paid for itself in days. We had a stored procedure that could not meet its SLA, DPA highlighted the issue and contributed to the resolution.
• We had a stored procedure that we were able to calculate as running in 9 milliseconds, unfortunately, we had transactions coming in 7 milliseconds, resulting in duplicate transactions, indicating that a mutex function was needed.

Incentivized