August 9, 2010 at 8:41 am
We are testing transactional replication. We have users at two seperate locations. Location1 will connect to the publisher and Location2 will connect to the subscriber.
I would like to not make any changes to our client application, but rather change the ODBC connection for the users at the different locations. Currently the way our dba set this up, I need to modify our application to say read from the subscriber but write to the publisher in the SQL statements.
Is there a way to setup replication on the subscriber in a way that I can only set the odbc connection at location2 to the subscriber and the subscriber will know to send all writes to the publisher?
Thanks!
August 9, 2010 at 8:48 am
The subscriber itself cannot do that. You should maybe look at Peer to Peer replication. Then you can update both subscriber and publisher.
-Roy
August 17, 2010 at 11:28 am
You can also "roll your own" two way Transactional Replication. Just setup up each SQL server as its own Publisher/Distributor and the other SQL Server as the Subscriber.
How to: Configure Nonpartitioned, Bidirectional, Transactional Replication (Replication Transact-SQL Programming)
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply