All geek questions in one place

Hot Hot / Warm Backup Server Replication Strategy (SQL Server 2005)

I have two identical servers with SQL Server 2005 and my application.

Strict requirements:

  • I should be able to update data on any server.
  • I should be able to disconnect any server without having to reconfigure anything in the database.
  • When the server is connected to the network, it should automatically synchronize with another server.

Notes:

  • I prefer options that would not add a significant load to the main server, if possible.
  • The two servers have a private network for replication, so bandwidth is not a problem.
  • It is enough that the data is outdated on any of the servers for a few minutes.

From what I read, my options are:

  • Transactional Replication with Renewable Subscriptions (Queued Update)
  • Replication Merge

Which configuration best suits my requirements?

+3
source share
2 answers

None of the current settings allows you to record both servers. Basically your only option is merge replication, as it allows you to upgrade both servers.

However, merge replication is the hardest to configure and run. You will need to make sure that the distributor has enough disk space to ensure that the distributor will not be exhausted at all times when one of the servers is down.

.

+1

?

, , Warm-standby , , , Primary.

, , .

100%, , , .

FedEx (.. "" ), , ; , FedEx'd, " ", , ; , , "", .

-1

Source: https://habr.com/ru/post/1704235/

More articles:


All Articles