>I have made some quick bench test for table with 160K records. There is really huge effect by SET DELETED setting: some simplect queries run for 20sec if ON against nothing if OFF.

This is what makes the big difference between 2.x and 3.0 and up. I really don't understand why they changed that at MS.

>But I didn't see any particular difference in regard to overall performance like SKIP,GO,SEEK etc.

That's good.

>So, probably it's not a bad idea still have SET DELETED ON and just reset it temporarily before running SELECT statement which will use DELETED tag:
>SET DELETED OFF
>SELECT ... Where ... NOT IN (SELECT ... Where Deleted())
>SET DELETED ON

Then, we might want to call a function to do all the SQLs and SET DELETE ON & OFF at one place only.

Also, since there is no BROWSE, at least not in my application, we don't have to do anything about it.

We should start Universal Thread for Benchmarks. :)