June 20, 2008 at 3:58 am
We are pretty new to setting up replication but need to do this now.
We have a client who wants to implement replication across 2 sites. Site A is the main site and publisher where pretty much all tables will be replicated on Site B, the subscriber. There are also some tables at site B which will be updated via a web interface which need to replicated back to A. So transactional replication with updateable subscribers method of replication looks to be the route to take.
The problem we have is that when we implement the suggested method, the wizard wants to create new columns namely a uniqueidentifier and quite possibly a timestamp field too. We don’t want this and can’t have it as the front end program which accesses the database will crash. Also we already have fields on each table which are unique and timestamp log fields also which could be used instead.
My question is - is it possible to setup transactional replication with updateable subscribers and selecting our own fields as unique identifiers rather than having new fields created and if so how?
June 20, 2008 at 11:48 am
you should look at "peer-to-peer" replication
* Noel
June 23, 2008 at 7:12 am
Thanks. Hadn't looked at this so will do some testing.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply