ouch! if at all possible, get control over the production indexes --
document what indexes are required and what they should be named in order
for your product to perform properly, then supply a configuration validation
option. i can't see any justification for a required index to not exist in
production, anymore than a customer or dba could justify dropping or
renaming constraints, tables, views, etc.
- mcs
"Thomas Kellerer" <spam_eater_at_gmx.net> wrote in message
news:bodhq5$1c6q3a$2_at_ID-13919.news.uni-berlin.de...
> Yes and no :-) We don't always have control over the index names that get
> installed into the production environment, but we do have control over the
> columns used....
>
> mcstock schrieb:
>
> > wouldn't it be better (clearer, more reliable) to use a hint to force
the
> > index usage?
> >
> > -- mcs
> >
> > "Thomas Kellerer" <spam_eater_at_gmx.net> wrote in message
> > news:bod7m6$1bu8rt$1_at_ID-13919.news.uni-berlin.de...
> >
> >>Prince Of Thieves schrieb:
> >>
> >>
> >>>Select c.clridx, n.price, n.perprice
> >>>from clr c, sprice_clrsku n where c.styleidx = 1164
> >>>and c.styleidx = c.styleidx and c.active = 1 and c.colouridx > 0 and
> >>>n.spidx(+) = 163
> >>>and n.clridx(+) = c.clridx order by c.clrcode;
> >>>
> >>>Notice the line "and c.styleidx = c.styleidx "? Why did the author set
> >
> > this
> >
> >>>SQL like this? Is this to accomplish something I do not know about?
> >>>
> >>
> >>I'm doing this pretty often as well. Mostly because you can force Oracle
> >
> > to use
> >
> >>an index on that column by including it this way. We have seen radical
> >
> > changes
> >
> >>in the execution plan by adding conditions like that.
> >>
> >>Thomas
> >>
> >
> >
> >
>
Received on Thu Nov 06 2003 - 07:44:15 CST