Are you looking for advise or are you testing us?
lets do that in slow moion:

You get the hightst current key at 13:00:00:00, it's 12345.
I get the highest key at 13:00:00:01, it's 12345!

you write your record with a PK of 12345 at 13:00:00:02
I write my record with a PK of 12345 at 13:00:00:03

I will get a duplicate key error.

If you see it any other way, I relly would like to know.


Peter


>Can either of you please support your claims? I am not locking, because I don't need to lock. Locking takes time, locks get left in place, locks cause things to wait, and locks are not as portable to an SQL server. (I don't necessarily want to use an identity field.) Also, algorithms that use locks need to flip the alias around, and you then run the risk of it not getting flipped back to the right one.
>
>So, do you guys still think it can fail? If so, please show steps.
>