>Hilmar,
>I tested the set exact status using a single table query.
>For character field joins, off course you need to have exact on.
>But what I've discovered is that with set exact off, a query runs faster and nothing more.
>Yau
Your claims warrant some further investigation.
I just did a few tests, both with a single table and with a join of 2 tables (joined on an Integer field). In the 2-table join, I tried both keeping the tables open, and closing them before the SELECT. I noted no significant difference in speed.
I therefore suspect that you had interference from "buffering": if you repeat the query a second time, part of the table is already in RAM. I suggest you repeat the tests
several times to avoid this.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
