Network Management

Using the SolarWinds Database Response Tool to troubleshoot database connectivity

The Database Response tool was developed to assist in troubleshooting SQL latency and database connectivity.

First published date

11/14/2023 10:39 PM

Last published date

11/13/2025 4:09 PM

Overview

When you suspect database connection or latency issues, please follow the steps in this article as it describes the Database Response tool, which was designed to assist in troubleshooting SQL latency and connectivity.

Product section

Network Performance Monitor

Resolution

Environment 

  • The Database Response Tool is located here:
    C:\Program Files (x86)\SolarWinds\Orion\SolarWinds.Diagnostics.DBResponse.exe
  • This tool will be present on all Orion Servers.
  • This tool uses the SQL Connection String set by Configuration Wizard.

Detail 

  • Launch SolarWinds.Diagnostics.DBResponse.exe from the Orion Installation directory. The default location is as follows:
     C:\Program Files(x86)\SolarWinds\Orion


NOTE: In version 2023.3.0.Default Path: C:\Program Files\SolarWinds\Orion. The name of the application was changed to SolarWinds.Diagnostics.DBResponse.
image.png
There are 2 settings here: Repeat and Interval (minutes). Repeat sets the number of times you will test and Interval sets how long you will wait between tests.
A Repeat value of 0 will execute once. In the following example results, five tests were used, occurring every six seconds.

  • The statistics displayed are the cumulative results of all tests.
  • The connection results are probably the most important. 
    • Results over 300 ms will cause performance issues, and results over 1000 ms will cause crashes.
    • The cycle statistics (cycle meaning, the time it took to connect to the database, query data and return the results) will show you how long each cycle took.
      • 1000 ms is a good benchmark for this, and, 10,000 ms is where you will begin to see issues.
  • If you see one query taking an unusual amount of time, you may want to check that table for index fragmentation or to see if it contains a lot of data.