Timeline for Oracle Autotrace vs Explain
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 16, 2015 at 15:06 | vote | accept | Jacobm001 | ||
| Jul 16, 2015 at 14:19 | answer | added | thatjeffsmith | timeline score: 6 | |
| Jul 15, 2015 at 19:45 | answer | added | Justin Cave | timeline score: 5 | |
| Jul 15, 2015 at 18:40 | history | edited | Jacobm001 | CC BY-SA 3.0 |
added 140 characters in body
|
| Jul 15, 2015 at 18:33 | comment | added | Jacobm001 |
@JustinCave: Woops... Should have paid more attention to what I allowed spell check to replace. I meant to say autotrace, which is a tool built into SQL Developer just like explain.
|
|
| Jul 15, 2015 at 18:31 | history | edited | Jacobm001 | CC BY-SA 3.0 |
Originally typed traceroute instead of autotrace
|
| Jul 15, 2015 at 18:29 | comment | added | Justin Cave |
What "traceroute" are you using? Normally, traceroute is an application that tracks network hops not something dealing with query plans. Are you comparing actual vs. estimated query plans? Or is this some third party utility with an unfortunately confusing name? As an aside, I would not say that B is obviously more efficient than A. It's certainly possible that's the case. But a cost that is too low is just as likely to indicate a problematic query plan as a cost that is too high.
|
|
| Jul 15, 2015 at 18:25 | history | asked | Jacobm001 | CC BY-SA 3.0 |