I have this scenario:
There exists one database(about 70GB).
At the same time, this database will be attached to the two SQL Servers 2005(x64), Standard editions. These servers are a few hundred km far away from each other.
Different applications will connect each SQL Server, these applications will modify data in this databases. It means that during this time the databases will have some different data.
We need to replicate these changes to these databases on both SQL Servers. So with this replication the databases will have the same data.
The data should be visible as soon as possible, so I am thinking about Transaction replication.
Is it possible, please, to do it with Transactional replication? What is your opinion on how to solve this?
I have tried this:
Server A as a publisher of database X and Server B as a subscriber of database X. This worked fine.
Server B as a publisher of database X and Server A as a subscriber of database X. I was not able to do this operation. There was an error: I cannot drop a table …. because it is being used for replication. So I suppose SQL Server A cannot apply the first
We cannot use Updatable Subscriptions for Transactional Replication because the structure of the tables cannot be changed.
We cannot use Peer-to-Peer Transactional Replication because it is only in Enterprise version.
Thank you ve
View Complete Post