Re: re:choosing idx to use

Ann Barnes@letterkenn-emh1.army.mil writes: |> |> When you create a composite index, the first field is also, effectively an |> index of its own. This was mentioned in the query optimization article here |> yesterday, but perhaps not specifically stated. Actually we have found in |> our ancient version of Turbo/SQL/4GL, that putting indexes as you have |> slows down the queries; we had to delete the index on _001 alone to speed |> up processing. Perhaps it is a quirk in our ancient versions, but it |> helped. That is due to the way the "old" (rule-based) optimizer did its job. 4.0 saw the introduction of the Cost-Based optimizer, which takes a completely different approach to choosing access strategies. Dave