2015-12-21 12-13-48
Hélio Cardoso
Execution Plan and SQL code
1308
Views
9
Comments
On our RadarOn our Radar
Aggregates & Queries
This use case is for the developer persona.

With the cloud solution developers lack control of what's going on at the DB, i suggest making the execution plan and sql code available, maybe Lifetime will be a good place to put it.
Execution Plan is an important part of determining if Indexes need to be added!

J.Ja
Wouldn't it be technically difficult to extract the execution plan from the underlying database? Let alone that depending on what the db engine thinks is in the tables, the excution plan may vary from invocation to invocation!
Mmm, sorry to necromance this idea, didn't see it's rather old.
It's not hard to get the execution plan itself, but you are right that it does vary based on a variety of factors.

It would still be useful much of the time to see obvious things... like if you always search on an un-indexed field, that will always show as an issue.

J.Ja

This is a old Idea, but really usefull especially on a PaaS/Sentry environment, so I'm surprised by the low Likes count. It has the status 'on our radar'; hopefully this functionality gets its place in the the ServiceStudio or LifeTime.

Happy LowCoding!

Matthias

Merged this idea with 'Add New tab Query-Execution Plan in SQL' (created on 05 Jan 2023 08:25:32 by Ramesh Subramanian)

Add new tab Query-Execution Plan. That would help for optimize query in OS side.


Merged this idea with 'SQL Diagnostic Tool for Performance Bottlenecks in Aggregates/Advanced SQL' (created on 18 Aug 2025 11:49:05 by Leonardo Elias)

It would be highly beneficial to have a built-in tool or configuration within Aggregates/Advanced SQL that allows users to diagnose SQL queries and identify which parts of the "SELECT" clause are causing delays in database response times.