You can use "set identity_insert tablename on" to manually set an
identity field.
Kevin
_____
From: Jochem van Dieten [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 11, 2003 9:00 AM
To: CF-Talk
Subject: RE: Primary key preference quick poll
Michael T. Tangorre said:
>> In many places order number etc. has to be a simple sequential
>> number because of accounting regulations.
>
> I do not think you are correct in your comment about order numbers
> having to be sequential.
I only know for sure about certain Dutch regulations regarding order
and invoice numbers, but I thought they originated from the EU.
>> Why not?
>
> You can not manually set a value in a int field that is an
> autoincrementing identity.
That might be the case with certain implementations, but it is not a
feature I see in SQL 200x for the IDENTITY datatype.
Which implementations are you refering to?
>> Doubtfull. The algorithm for creating a UUID is both time and
>> hardware dependent.
>
> I think Tony meant that if you had other records in other tables for
> instance that led you to the key, you could get the value and
> re-create the record that was lost (barring any constrints that
> would be in place...).
That would work quite the same with a standard IDENTITY field.
Jochem
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
