Our company is utilizing Identity(1,1) clustered primary index in SQL Server 2016 Enterprise, and will eventually deploy into the Cloud (Amazon AWS, Google Cloud).

  1. Is there any issues utilizing Identity Column in Azure SQL? If were ever horizontally elastically scale databases, we can manage identity columns using range identities or location/storage ids,

  2. Are there any issues deploying Microsoft SQL server Identity Columns into Cloud in general (Google or Amazon AWS Cloud)? We heard of identity numeric gaps as in any SQL Server Environment, and how often will they occur in cloud?

  3. How about Amazon AWS?


2 Answers 2

  1. No issues with IDENTITY or SEQUENCE in Azure SQL Database, or SQL Server on Azure VMs.

  2. If you move to a federated design, you should not use the IDENTITY or SEQUENCE value as the only key of any federated table. If your key is something like (TenantId, SequenceVal), then you can have duplicate SequenceVal, but still allow the rows to be globally unique. Otherwise you can use ranges, as you propose, or somehow interleave the values.


3) There are no issues utilizing clustered Identity index for Amazon AWS, I contacted Amazon cloud technical support.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.