Re: Forsing certain execution without hints ...

This is not a response to your question, but it's an alternative approach.

We defined a "star schema" to hold data for loading into Cognos, and for reporting purposes.

The dimension tables each had a defined primary key (which implies an index in Oracle).

The fact table had foreign keys defined for each reference to a dimension, and, in addition,
a primary key defined made up of all the foreign keys.

The data loaded awfully fast from this schema. In fact it took less time to load this schema from the original source, and then load up a cube than it took to load the cube straight from the original source!

I'm not saying this will happen in every case, but there are times when this is exactly the right approach.

And we used neither hints nor tricks!

sergey_s_at_my-deja.com wrote in message <8uuie1$gsk$1_at_nnrp1.deja.com>...
>What are some of the "tricks" that I could use to influence a certain
>execution path in Oracle besides using the hints? I know of things like
>appending a blank string ('') to avoid an index, or doing
>something "dummy" on an indexed column to force the use of an index
>(col > 0). What are some other things that can cause Oracle to use
>indexes, or choose certain join methods, etc (besides the hints)?
>
>I have a group of Cognos users using the visual query builder. If I
>edit the query manually (by adding hints) then Cognos disables the
>visual query builder. Noone knows if there is a way to add hints
>through the visual builder. However, we can add "tricks" in the where
>or select clauses through the visual builder and not loose the ability
>to use the visual builder the next time we get into Cognos. So, it's
>all about the users being able to use their visual builder all the time
>and at the same time being able to influence the best execution plan.
>
>Thank you!
>Sergey
>
>
>Sent via Deja.com http://www.deja.com/
>Before you buy.
Received on Wed Nov 15 2000 - 13:22:32 CST