Timeline for Merge replication Identity columns for already existing databases
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 28, 2017 at 20:47 | comment | added | NismoGTR05 | No, there should not be any issue at your central location as records from two different sites will become unique with the Host_Name in it. Ex: 1, John, RowGUID, Server1 1, Steve, RowGUID, Server2 As you can see, eventhough the ID column is same (i.e. 1) row at central location is still unique with RowGUID and HostName. | |
| Jun 28, 2017 at 3:17 | comment | added | Vikram Dwarakanath | Hi HP, Thanks for the inputs, appreciate the quick response. Quick question - Yes, the row would be unique at the central location with the column combination, but will there not be a problem inserting the record at the center, because the identity column value would still be the same with NOT FOR REPLICATION on? So I will be attempting to insert separate unique rows (with the combination of row GUID and host name), but with same ID column values. NOT FOR REPLICATION is needed because the ID column is referenced in many other tables for joins. | |
| Jun 27, 2017 at 12:23 | history | answered | NismoGTR05 | CC BY-SA 3.0 |