Skip to Content (Press Enter)
Back to Ideas
48
Like
Follow Idea
Queries execution time measurement
1000Views
5Comments
On our RadarOn our Radar
Aggregates & Queries
It would be interesting to have in all Simple/Advanced queries the information about the execution time of each query when we test it in the Service Studio. It could be just a label next to the test button. This way the developer can always keep in mind the issue of the application performance, starting in the unitary level of each individual query.
06 Apr 2012
Copy link to comment
I  would go farther with this idea and suggest the implementation of a time watch where you could measure the time that some action takes. Soming like a start and stop watch points.
Like in matlab there is tic and toc functions and in C Stopwatch.
18 Nov 2013
Copy link to comment
A lot of this is available in the Lifetime Performance Monitoring results.

J.Ja
10 Dec 2013
Copy link to comment

You can use the action RunJavaScript from HTTPRequestHandler extension with the code:

"console.log('"+ CurrDateTime() +"');"


RM

07 Mar 2019
Copy link to comment
Merged this idea with 'Integrated Execution Time and Query Plan in Service Studio for SQL and Aggregates' (created on 07 Jan 2026 11:09:31 by Neha Agrawal)
08 Jan
Copy link to comment
2023-12-11 08-54-13
Neha Agrawal
Champion

Provide real-time performance metrics (Execution Time) and Database Execution Plans directly inside the Aggregate and Advanced SQL editors after running a "Test" query.

  1. Advanced SQL: Add an "Execution Plan" tab next to the results and display the total execution time (ms) in the bottom status bar.
  2. Aggregates: Show the Execution Time upon testing and provide a placeholder in the Properties tab to view the generated Execution Plan similar to Executed SQL.
  3. The Goal: Eliminate the need to switch to external SQL sandboxes or SSMS to identify slow-running queries, missing indexes, or costly table scans.

Value Proposition

  • Proactive Tuning: Detect performance bottlenecks during development rather than after deployment.

  • Efficiency: Reduces context-switching between Service Studio and database management tools.

  • Optimization: Makes the performance impact of complex Joins and Filters immediately visible to the developer.

07 Jan
Copy link to comment