July 21, 2003 at 12:27 pm
My company has offices all around the globe and we have a requirement that any location should be able to generate orders.
We would like to implement Merge Replication for the same. Each location's order numbers should be sequential without gap. To accomplish this, we have considered adding a field (origin location) to the order table
that, when combined with the order ID, will uniquely identify a row in the
table. This way, both USA and Sri Lanka may have generated order ID 5000
at the same time, and these rows will merge without conflict. Are there any pitfalls that we should be aware of? Can you suggest any alternative ways of achieving this
goal?
Any thoughts are greatly appreciated.
July 24, 2003 at 8:00 am
This was removed by the editor as SPAM
July 24, 2003 at 5:51 pm
That will work as long as you make it the primarykey. I know they aren't easy to read, but uniqueidentifiers are great for merge replication. They also don't meet your requirement to have them sequential.
Andy
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply