Large Identifier Uniqueness Across Table We use NEWSEQUENTIALID to generate uniqueidentifier as table ID.
Issue is raised after server reset as the seed of it is modified and sequentiality breaks.
Is there another suggested solution to achieve large identifier uniqueness for a table?
Thank you
Perhaps look into Jimmy Nilsson's COMBs? Discussed here: https://stackoverflow.com/questions/1155454/performance-value-of-comb-guids
Or, if you don't need uniqueness over several SQL Server instances, just some int-type with a sequence or identity? (As suggested by Mo64.)
The fact that NEWSEQUENTIALID() is &quot;re-seeded&quot; at re-start isn't anything we can prevent, AFAIK.