Re: Indexing Question

kevin.james.campbell_at_medtronic.com wrote in message <345F599D.388D_at_medtronic.com>...
>I have an ORACLE SQL statement that is in need of one or more indexes.

You need to know the degree of granulity in the data so you can base your indexing strategy on the columns that will give you the best resolution. Basically you want the index to "show" your query a sensible number of rows to choose from. You also need to consider the indexing load on your tables when modified.

You want an index to always "show" your query about the same number of rows as the table grows. It is likely that you will get adequate performance from your query if it can see less than 1000 rows in each table. The tables joining on Contact are relatively easy; if they contain or will contain more than 1000 rows each then index on the key field joining with Contract. Your date restriction doesn't seem to do anything as both dates are the same; is this intentional?. I assume you want between dates. If your Contact table is big then you will need to answer questions about ganulity before choosing column(s) to index.

Don Fraser
Aotea Software
Aotearoa (NZ) Received on Wed Nov 12 1997 - 00:00:00 CST