Execution Plan and SQL code
792
Views
5
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.
2019-11-12 17-31-26
Justin James
mvp_badge
MVP
Execution Plan is an important part of determining if Indexes need to be added!

J.Ja
2020-09-15 13-07-23
Kilian Hekhuis
mvp_badge
MVP
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!
2020-09-15 13-07-23
Kilian Hekhuis
mvp_badge
MVP
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
2022-09-05 17-58-21
Matthias Preuter
mvp_badge
MVP

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