What to Look for in Execution Plans: Databases for Developers: Performance #3

[@hindimotivation5231]

I am not able to understand the autotrace part where view part individual elapsed time is 728 micro seconds. How this was calculated , Please elaborate. Thankyou.

[@hindimotivation5231]

One more doubt , in 3rd sort operation why it dont have any elpsed time as you said in video.

[@TheMagicofSQL]

I'm not sure exactly what you're referring to - please clarify. In any case, this value comes from the database measuring how long the operation took.

[@TheMagicofSQL]

Again, I'm not sure exactly what you're referring to.

[@atulgupta9301]

Very well explanation

[@chocOneOOne]

as usual Chris' lego game is on point

[@amitkaushik3569]

Nice explanation.

[@albertogonzalez5114]

very useful, thanks!

[@a.useronly2266]

Amazing

[@VEERSINGH-er9so]

Great explanation !

[@ikacherful]

Somewhat newbie DBA here. This information is beyond helpful - thank you so so much Chris!! I have a question about Oracle SQL Developer - is it possible to run autotrace without actually executing the SQL statement as well (I'm working with big tables in production)? I know it is possible through SQLPlus via traceonly option, just cannot tell if it's possible in Oracle SQL Developer as well. -Thank you

[@TheMagicofSQL]

To get the plan's execution stats you have to run the SQL statement! set autotrace traceonly in SQL*Plus does execute the query, it just suppresses the output. The autotrace option in SQL Developer also executes the query, but there's no option to see the results. If you have a long-running query and you want to see the plan before it finishes, check out the SQL monitor. You can access this in SQL Dev via Tools -> Monitor SQL. Note you need appropriate licenses to use this!

[@ikacherful]

@@TheMagicofSQL I see, I will definitely try this option. Thank you!!! I really appreciate it.

[@ThuNguyen-g6b9b]

goddang this is gold

[@TheMagicofSQL]

Thanks! Glad you found this useful