I have the following transactional replication setup:

Windows Server 2008 with SQL Server 2008 Enterprise

Server A: Master, has a database with a table, publisher
Server B: Slave, subscriber (Backup server)

For backup (and read only access to B during down time), transactional replication is a good solution. However, during downtime of A, I want the application to read and write to the database on B. It is possible to backup B and restore the content to A, but is a merge replication a better way?


for backup purposes I would implement database mirroring. if read access is required then using database snapshots could help.


i believe that merge replication would work to eliminate the need to backup/restore from B to A, but the performance penalty would be considerable. if the base is small then it would be fine.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.