SolarWinds Database Performance Analyzer solves problems that OEM can't even recognize are occurring
December 14, 2020

SolarWinds Database Performance Analyzer solves problems that OEM can't even recognize are occurring

Anonymous | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with SolarWinds Database Performance Analyzer

[SolarWinds Database Performance Analyzer is] used to monitor the performance on mission critical application databases, both bespoke and packaged applications. For bespoke applications, it is used to ensure that the code developed by our technology partners meets or exceeds the defined SLAs, as well as to alert of problems before they become critical issues. For packaged applications, it has been used to extract detailed information on performance issues, such that we were able to log extremely detailed issues with the vendors, such that they have all of the information needed to correct the underlying issue. For example, we were able to extract the run time of stored procedures, including all of the SQL statements executed, such that the vendor was able to pinpoint the issue rapidly and provide a resolution.
  • Maintains historical SQL execution data, enabling forensic analysis
  • Has the ability to slice and dice the data so that you can drill down to the execution of a single SQL statement being executed by a stored procedure
  • Alerts to when the consumption pattern changes
  • Shows historical average run times against the current, illustrating problems when they arise
  • Provides tuning advice based on best practices
  • Everything is displayed visually, if you need detailed metrics, you have to extract manually, it could use a report writer with export to Excel.
  • When a SQL statement is very long running, i.e. longer than the display interval, the display says that there are no statistics, it should on the other hand, show that the SQL statement is still running.
  • When you name a SQL statement, it should be by DB, rather than global
  • 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.
Very appropriate for use in performance testing
Very appropriate for alerting to performance issues before they become critical
Can be challenging when monitoring an Oracle active-active RAC database, as each instance is effectively a separate database.