It basically is an internal set filter to On !Deleted(). If you don't have a deleted tag, and you have set filter on, your queries are never totally optimized. Other things take a hit as well. This is why it is a good practice to have a deleted tag...




>Hi Folks,
>
>This stuff about SET FILTER got me wondering last night how SET DELETED ON works. I figured that it is really an internal SET FILTER. Does anyone now for sure? If the case, should you avoid SET DELETED ON? Wouldn't that slow it down abit?
>
>And without starting another thread, what is the final desicion on the DELETED() index expression, does that speed up SET DELETED ON?. IMO, this should be another document, because there are plenty of long (confusing, and difficult to read) threads on it