>Hi everyone,
>
>One solution to avoid duplicate keys when you delete a record and add a new one with the same ‘business key value’ is to use surrogate keys (integer values).
>
>But, if i want to enforce unique values for my business key (Ex: social security number) using candidate indexes, i find that problem again: Duplicate keys.
>
>Any workarounds? I have been updating ‘business key fields’ with negative random values after deleting the record. It works, but it’s a strange trick, isn’t it?
>
>How do you solve this?
>
>Thanks,
>
>
>Juan Carlos Jaramillo.

Social Security Numbers are not unique. Duplicate numbers have been issued but the US government.