Re: how to force the use of an index?

possibly using set optimization low would cause the cost estimate to be lowered and the optimizer would try to be less efficient, and get your index path. m. pfadenhauer wrote: > hello there, > yes indeed the most trivial case is a missing 'update statistics'. but i > can tell you i did execute 'update statistics' but the result didnot change. > 'sqlexplain.out' still says it used an sequential scan to get the data. > so my idea was to force the optimizer to use the index but the directive was > ignored. > maybe there is an (syntax-)error in the directive, but i don't know where > (help!). > > btw, which SQL manual do you mean and which hint section. i got lost in the > manuals.... > > thanx > markus pfadenhauer > pfadenha@informatik.tu-muenchen.de > > NSI001 schrieb in Nachricht <19980924133811.26380.00001124@ng39.aol.com>... > > > >Hallo, > > > >the most trivial case would be that you didn't do an update statistics. > > > >Otherwise you should have a look at the "hint" section in your SQL manual > > > >Klaus Nonne > >nsi001@aol.com