Thought I had blogged about this before but couldn’t find the reference. Tanel Poder put together a nifty tool that takes an explain plan with execution stats and maps it out such that he steps that take more time are bigger and those that take less smaller. Some small steps might be so small they aren’t even visible which is fine. Why should we see them if they are so fast?!

http://tech.e2sn.com/apps/planviz

I’m also wondering if DB Optimizer could harness this type of functionality. Currently the graphic execution plan nodes are all the same size like on the left, but maybe the nodes could be sized by time as well:

Not sure my mockup is the prettiest example but I think it at least shows the idea.

Kyle Hailey
Uncategorized