James writes "We are developing a distributed application using SQL Server as the back end.
We do not want to use Identities for the primary keys. We are planning on making a "NextID" table that consists of each table name with the "next" ID that should be used.
Is there another way on managing primary keys without using Identities, especially when concurrency is an issue?
By all means, use the natural key. Failing that, consider the amount of traffic on the system before you implement any solution where every transaction will be going to the same table and updating the same row.
Managing your own primary keys
Forum Locked
Posted - 07/12/2002 : 09:13:35
