>>Juan;
>>
>>Do you mean that if you have a person with Social Security # 111-11-1111, and then delete him, that you can't later add him, or another person with an SS# of 111-11-1111? If that's what your problem is, you can put a filter on your candidate for for NOT DELETED(). Then when a record is deleted, it is removed from the index as well.
>>
>
>Hey that's a cool trick that I hadn't thought of before. But wouldn't it be better (for rushmore optimization) to add the deleted function in the index expression instead of using a filter.
>
>Maybe it doesn't make any difference... Just a thought I had.

Yes. Filtered indexes cannot be used by Rushmore.
Filters on indexes also can slow things down quite a bit.
Also, NOT DELETED() is slower than just DELETED() alone.