azure - Best Table Structure Design for Synchronization or Replication -


dears,

i have choose following table structure common tables in application :

create table [dbo].[equipm]( [id2] [uniqueidentifier] not null, [id] [bigint] identity(1,1) not null, ...... ......   constraint [pk22_equipm] primary key nonclustered ( [id2] asc)with (pad_index = off, statistics_norecompute = off, ignore_dup_key = off, allow_row_locks = on, allow_page_locks = on) on [primary]) on [primary] textimage_on [primary] 

explanation:
guid primary key not clustered. use newsequentialid()
bigint unique , clustered index, , used relations other tables.

question 1: structure optimal ?
question 2: shall use guid primary key , relations other tables since use synchronization or may replications in future ? if yes, consequences should keep in mind ?

extra information
above design used in application support multi user signing different geographical locations, use sql azure sync databases between main office of company , branches.

i hope post clear
thanks


Comments

Popular posts from this blog

amazon web services - S3 Pre-signed POST validate file type? -

c# - Check Keyboard Input Winforms -