We are reconsidering placing a second SQL Server in our remote office. In order to have all data available we would like to implement transactional replication. The scenario will allow us to have read/write options at both offices. I will adjust the SF application to recognize which server to use based on the physical location of the user. That should not be a problem.



Now, we also have a nice little setup for incrementing a number of different record IDs (order ID, packing list number, credit memo ID, etc.). I created a NextID table that allows us to have some nice control over these numbers used to track our various records. It works great.



Enter transactional replication.



What will happen to our nice NextID setup? In what ways do I need to change our approach in order to have the same basic functionality. I fear that a person in the remote location will create a new record and be handed an ID that is the same as the ID just handed out to the user in the main office. Impending crash detected.



Thanks for your input!!

Bill