Re: Best "how to index" docs/books

From: Carol Dacko <dackoc_at_gmail.com>
Date: Mon, 13 Jan 2020 21:09:29 -0500
Message-ID: <CABUxq=fQd7R4G3GDe2x4SPwVfjkqP2GwSE8fC_9qPP9uqPrMTA_at_mail.gmail.com>



I agree with Cary. It just takes time to make it part of your routine.

Best,
Carol

On Mon, Jan 13, 2020 at 6:28 PM Cary Millsap <cary.millsap_at_method-r.com> wrote:

> Dan's book #1.
> Tapio Lahdenmäki's book #2.
>
>
> Cary Millsap
> Method R Corporation
> Author of *Optimizing Oracle Performance <http://amzn.to/OM0q75>*
> and *The Method R Guide to Mastering Oracle Trace Data, 3rd edition
> <https://amzn.to/2IhhCG6+-+Millsap+2019.+Mastering+Oracle+Trace+Data+3ed>*
>
>
>
> On Mon, Jan 13, 2020 at 2:33 PM kyle Hailey <kylelf_at_gmail.com> wrote:
>
>>
>> What are the best docs or books out there on methodologies for Index?
>> The first past approach is just to look at execution plan, see
>> where there are full tablescans scanning significant # of rows or blocks
>> with predicate or join filters that filters out most of the rows. Then
>> extending that index opportunity to other SQL and seeing which columns
>> might be included in the index and what order. I like this description from
>> a PostgreSQL extension
>> https://rjuju.github.io/postgresql/2020/01/06/pg_qualstats-2-global-index-advisor.html
>> .
>>
>> Many years ago, Mogens Nørgaard recommend Dan Tow's book "SQL Tuning" to
>> me for SQL tuning methodologies and to this day it has been the best
>> example of a prescriptive , step by step process, to find the best (or near
>> best) execution plan for a SQL statement, and ended up helping me lead a project
>> to implement it in software
>> <http://dboptimizer.com/2011/07/08/woohoo-vst-takes-the-next-step/>.
>>
>> Would like to find something similar for indexing to find
>> optimal opportunities for adding indexes.
>>
>> Feel free to say what not to read. Knowing what not to read can be
>> important as well.
>>
>>
>> Thanks
>> Kyle
>>
>>
>>

--
http://www.freelists.org/webpage/oracle-l
Received on Tue Jan 14 2020 - 03:09:29 CET

Original text of this message