SQL Server - PRIMARY KEYS (autoincrement)...

[MarkatTekTips2004]

In SQL Server 2000, I'm looking for input as to how to set up primary keys (PKs).

Is it safe to use the IDENTITY feature using AUTOINCREMENT as a setting for a PK, or is it best to generate my own and check for dups?

My concern is whether SQL Server at any point will taint the numbers used as the PK -- because as you know, these PKs are going to wind up linking into (relating into) other tables (e.g. client orders).

Certainly it's vital that the clientID not get lost/changed during any regular DB maintenance or use.

Any input would be appreciated.

 

[donutman]

The use of an identity column as the PK is best practice. I doubt that any attempt to make the system more reliable is a futile exercise.
-Karl

[red] Cursors, triggers, user-defined functions and dynamic SQL are an axis of evil![/red]
[green]Life's uncertain...eat dessert first...www.deerfieldbakery.com[/green]