>>My problem is this, the data is on a NT 4 box and I have 2 do queries/subtract info out of this table. I'v tried SELECT but that was realy very, very slow. Then I used the SET FILTER. A lot better, but far to slow.
>
>Whether talking about SQL Select, excersizing, or sex, the rule of thumb is "if it hurts, you're doing it wrong". Try SYS(3054)to see if you are optimized properly.
>
>Are all fields in "join" and "where" clauses indexed?
>Are you using "Distinct" (which searches all fields) where a "Group By" would work?
>Are your joins causing a cartesian product which will then be reduced via a "Distinct" or "Group By"?
>Are you using poorly functioning compares such as "$", Select within a Select, or a UDF?
>
>Anyone on my team has to live with the rule: "Set a Filter, Lose a Finger". It may have appeared faster than your Select, but with optimization that will change.
>
>jt

Hi J

Thanks for these tips, i'll try them. One more thing, if I would use a ORDER command in the SQL select, will it be slower.

Thanks

W