January 5, 2004 at 11:42 pm
Synchronized Databases.
We are trying to support two existing databases that are completely synchronyzed. Each database is on different servers, and are updated/inserted/deleted by different users.
We tried using transactional replication with updateting subscriber, but we encountred problems with managing the identities fields.
We are looking for the optimal way.
Thank you in advance
January 6, 2004 at 5:52 am
You can change the identity property to NOT FOR REPLICATION and assing different seeds and values to each server, or you can also change to Merge replication that will manage identities much better.
January 7, 2004 at 6:25 am
With Merge replication you will still have to manage your Identity columns by setting up Identity ranges. You could however set up a composite key based on for example : server name and an int column (set for non-Replication) both would be set up as primary keys. Something like
Int Varchar
1 | SERVER1
The above example would allow you to NOT have to worry about Identity ranges.
Are these two servers always online? What is the location of these servers to one another, east coast west coast, or within the same Domain or sub-domain?
Merge would be a great solutions but it is much more complicated to set up and to administer. Transactional is much easier to set up and in my opinion more effective for certain circumstances.
Either way they both will work however it’s important to really understand your environment prior to setting up any type of replication.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply