Re: Q: optimizer does the wrong thing on join

> ppr@deckard.hb.north.de (Patrick Preuss) writes: > we have a join with several tables, written with the most restricting table > stands at the top (the right thing, I guess). > What does the optimizer do? He just flips the order, and scans the biggest > table first, sequentially!!! Is this a problem for Update Statistics? This depends heavily on what version you are on - which you as so many others hide for us as well as you can. You may look at many very reasant posts for all the strange tricks people have been using to trick the optimiser. It's a very sad state of affairs that this had to be done. It's a significant part of the usefulness of relational databases that you shouldn't have to spesify indexes or any other parts of access routes to the data. However in version 7.1 of OnLine we have found that most of our problems can easily be solved with the proper update statistics command (including the high option for special fields). We had your problem on version 5.0 of SE where this is a documented "feature". Great..., but I belive also ver. 7.x of SE solves this although I haven't had the oportunity to test that yet. Nils.Myklebust@ccmail.telemax.no NM-data, Aasesvei 71, 1300 Sandvika, Norway My opinions are those of my company