Quantcast
Channel: SQLServerCentral » SQL Server 2014 » Administration - SQL Server 2014 » Latest topics
Viewing all articles
Browse latest Browse all 6525

Replication with updateable subscriptions

$
0
0
Hello, I am wondering if anyone has been in a similar situation and if so how they resolved it.I have been asked to look at setting up replication between SQL 2008 R2 Enterprise and SQL 2014 Enterprise such that data can be amended at either the publisher or subscriber and the amendments are replicated with as little latency as possible. That part does not seem too difficult; however there are a couple of complications that I need to take into account. The web application that these databases support allows users to create their own data tables in one of the databases and these tables would need to be included in the replication scenario as soon after creation as possible, and this would need to happen without interrupting user access to any of the databases involved.Within SQL there seem to be four types of replication, Snapshot, Merge, Transactional and Peer to Peer.Snapshot and merge replication don't appear to meet our needs. With snapshot replication the amount of data involved and the latency of applying the snapshot would make it far too slow. Merge replication is not suitable as it is for subscribers that are not always connected to the publisher, which is not the case here.My first impression of transactional replication with updateable subscriptions was that this would provide the means to do exactly what we require, data can be amended at both ends and new tables can be added without stopping user access to the database and without affecting the existing replication. Unfortunately transactional replication with updateable subscriptions is a deprecated feature, and according to the documentation I found regarding SQL 2016 it is not supported in that version so although it should work now we will need a rethink if we upgrade to SQL 2016.Peer to peer replication seems to meet some of our requirements, but for us has one big stumbling block, to add a new table to this type of replication requires all activity to be stopped on the replicated databases while the new table is added.If anyone has been in a similar situation and came up with a solution I would be very grateful for any advice you could offer.Thanks very muchIan

Viewing all articles
Browse latest Browse all 6525

Trending Articles