Re: A brief doc on 10046 tracing

i couldn't disagree more. part of good writing is focus. if everything that was put out there explored every detail of a given topic---->which would then turn into every detail about every related topic in the name of completeness, then there would be a bunch of dooda that no one would use.

a big part of being an oracle professional is being able to filter out what is and is not important to the task at hand. this paper is meant to be and /introduction/.

On 7/21/05, Juan Carlos Reyes Pacheco <juancarlosreyesp_at_gmail.com> wrote:
> Hi Robin, if you want an honest opinion about notes, I can give you
> one, and I expect be useful :).
>
> I think you need some examples and share some experience, I recently
> was breaking my head to optimize a query, and the problem was in the
> view the condition was wrong, and I didn't found that in the trace
> file I analyzed.
>
> So even when I don't scorn short explanations. To be useful, if you
> want to do something interesting for dbas, you must cover every point
> more deeply and share your experience in every point and with
> interesting examples.
> If you have to write a 15 pages pdf, then do it, but if you want to do
> something you can find better in documentation, I don't think you
> should waste your time.
> Good luck
> --
> http://www.freelists.org/webpage/oracle-l
>

--
http://www.freelists.org/webpage/oracle-l