HiLo or personality?

Question

I just wanted to get some opinions about primary keys - would it be better to use identification numbers / sequences or use the HiLo strategy (query for a large value and increase the minimum value for the application itself)?

Answer 1

If your application would use only one database, I would go with an identifier / sequence.

The only truly reasonable reason I've seen working with HiLo is when you can have two disconnected instances of your application that people can work with at the same time, and you need to reconcile the differences at some point.

Ex . You are working on a content management system where people can work on two different servers in different places, but at some point they should be synchronized.

Answer 2

If you are using SQL Server 2005/2008 with a large table (> 1 million rows), you can consider this , which references this . In certain circumstances, a problem arises with the identifiers scope_identity () and @@.

Of course, developing around the current implementation problem is not always the wisest solution.