we have three secondary database server in different cities and one primary server. my question is i want asynchronous transaction commit to all three database but primary key data conflict occur when commit to primary database...because same id can generate on all three server. then which technology is available for this kind of scenario for maintain primary key conflict issue...
Note-all three secondary server work as a 'replication publisher' and primary server work as a subscriber(primary replica of alwayson).
solution from my side- i commit the records on secondary server and i use some tricks on all secondary server like..server 1 (seed value = 1 increment by = 3),server 2 (seed value = 2 increment by = 3), server 3 (seed value = 3 increment by = 3)...according to this setting my primary key value never conflict....so please advice am i going right way or not ???