These pages cover ANTS Performance Profiler versions 8.0 to 8.6. Help for older versions is also available.

Skip to end of metadata
Go to start of metadata
Icon

Database calls view is only available in ANTS Performance Profiler Professional edition.

Database call performance data is not recorded when profiling in sampling mode.

The Database Calls view shows performance data for all the database calls your application made during the time period you have selected.

If a call was made multiple times, it is still shown only once in the database calls view, with timing and hit count data aggregated from each instance of the call.

The following data is shown for each database call, for the time period you have selected:

  • Query: The first line of the database query (excluding any initial blank lines). To view the full query text, move the pointer over the row.
  • Total time to first result (ms): The time taken (in milliseconds) until the query returned its first result.
    Where a call was made multiple times, this is the sum of the time to return a first result taken by all instances of the call.
  • Average time to first result (ms): The time taken (in milliseconds) until the query returned its first result.
    Where a call was made multiple times, this is the average time taken for each instance of the call to return the first result.
  • Hit count: The number of times the call was made.

When a query is selected, a yellow highlight on the timeline shows the period when the call was running. Source code for the selected query is shown below the list of queries, in SQL Source Code View.

Linking back to your code

To find out which of your code's methods ran a particular SQL query:

  1. In Database Calls view, select the query.

     icon appears on the right-hand side of the Query column.

  2. Click on the  icon.
    The display switches to the call tree, with the SQL query selected.
    You can scroll up the call tree to locate the query's .NET parent, and browse its timings to determine whether the problem lies in the way the query is called.
    For more information on understanding .NET method timings, see Working with the call tree.