Identity/Seed Values

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Joe Williams (joe_at_anywhere.com)
Date: 02/21/05 

Date: Mon, 21 Feb 2005 09:48:15 -0500

I have a question regarding using the Identity/Seed values. I have migrated
a number of tables form Access to SQL. In Access the identity/seed values
were called autonumbers.

The big problem with autonumbers in Access was that they could change at any
time on you, getting renumbered or sometimes even becoming negative values,
etc.

Now, in my application I have need for a unique number as the primary key AS
LONG AS THE NUMBER WILL NOT CHANGE IN THE FUTURE. I do not need it to be
formatted a special way, I do not need it to be sequential, etc. But I do
need it to stay the same after it has been entered.

So, my question is this: I know in Access i could not rely on the autonumber
to stay the same. Does the identity/seed value propoerties of a SQL table
have this same issue? Or can I plan on this value staying the same over
time?

Thanks

Joe

Relevant Pages

  • Re: Identity/Seed Values
    ... Identity values in SQL Server start at the seed value. ... increments by 1 and cannot be manually inserted or updated. ... > The big problem with autonumbers in Access was that they could change at ...
    (microsoft.public.sqlserver.programming)
  • RE: Identity/Seed Values
    ... "Joe Williams" wrote: ... > a number of tables form Access to SQL. ... > The big problem with autonumbers in Access was that they could change at any ... Does the identity/seed value propoerties of a SQL table ...
    (microsoft.public.sqlserver.programming)
  • Re: Append query to multiple tables
    ... LotsOimports wrote: ... > I was hoping to be able to code in SQL ... Then lose the autonumbers. ...
    (microsoft.public.access.externaldata)
  • GUI interface
    ... I am just braking into SQL and my company is upgrading ... form Access, to SQL 2000, is there an interface that will ...
    (microsoft.public.sqlserver.server)