Is anyone aware of any special requirement involving date fields and an
index?
I created a one-column index on a fairly large table involving a date
field. Then I tested a multi-table join involving the table with a where
clause that included TIME_PERIOD = '01-SEP-1996'.
Although I realize the index is not especially selective (it's always the
first day of the month), here's what surprised me. The query runs many,
many times long with the index than without. Furthermore, the TKPROF stats
show some huge number of rows scanned, many times the actual size of the
table.
In fact, the query runs faster if I disable all the potential indices than
it does with the date-field index on.
Any clues?
Thanks in advance for your help...
cheers--bruce
Bruce Douglas -- bruce.douglas_at_bridge.bst.bls.com
BellSouth Telecommunications