


Peer-to-peer replication is a solution oriented to Horizontal scalability at high availability, as it allows to manage many copies of data in more instances of the server, called “nodes”. Based on transactional replication, Peer-to-peer replication propagates data changes to all the nodes and almost in real-time. SQL Server provides 4 kinds of replication procedures: On the contrary, we will focus on the database replication procedures, that is, all those configurations that allow users to have all data being replicated on more SQL Servers, in an automatic and real-time way. In this tutorial we won’t talk about Failover Clustering or Availability Groups Always On, which both are database mirroring procedures with the main purpose of insuring the continuous availability of all services in a prompt way in case of disservices or server crashes. All of them are strategies and configurations whose purpose is, with different ways of acting, to make data always available to client applications, in case of crashes and disservices, or simply to replicate data in more geographic locations to increase accessibility and availability performances.

Microsoft SQL Server is a database plenty of features regarding replication, mirroring and failover clustering.
