Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
AskSQLTeam
Ask SQLTeam Question
0 Posts |
Posted - 2002-07-12 : 09:13:35
|
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?Thanks!" |
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2002-07-12 : 09:16:25
|
Yes! Use the table's NATURAL KEY....<O> |
|
|
dsdeming
479 Posts |
Posted - 2002-07-14 : 22:03:44
|
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. |
|
|
MichaelP
Jedi Yak
2489 Posts |
Posted - 2002-07-15 : 11:22:58
|
Another solution that works well with distributed applications is GUIDs.Look up unique identifier and NewID() in BOL.Michael<Yoda>Use the Search page you must. Find the answer you will. |
|
|
|
|
|