Q: optimizer does the wrong thing on join

Hi, 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? Thanks, Patrick -- Patrick Preuss :- on this side of the video screen ppr@deckard.hb.north.de :- on the other side "A just machine to make big decisions / Programmed by fellows with compassion and vision / We'll be free when their work is done / We'll be eternally free yes and eternally young." D.Fagen