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).
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,
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?
How about Amazon AWS?