All 7 Replication questions
More in Replication
What are the three main types of replication in SQL Server, and how do they differ? What roles do the publisher, distributor, and subscriber play in a transactional replication setup? How do you monitor the health and latency of a transactional replication setup to ensure subscribers are staying reasonably up to date? What steps are involved in setting up transactional replication for the first time between a publisher and a new subscriber? How would you troubleshoot a transactional replication setup where a subscriber has stopped receiving new changes entirely? How does replication compare to Always On Availability Groups for keeping data synchronized across multiple servers, and when would you choose one over the other?
Advertisement
Back to results for “Replication”
SQL Server › Replication

What is SQL Server replication, and what problem does it help solve?

Beginner

Answer

Replication is a set of technologies that automatically copies and synchronizes data from one database, called the publisher, to one or more other databases, called subscribers, letting you distribute data to multiple locations for purposes like reporting, offloading read traffic, or keeping remote offices synchronized with a central database.
-- Simplified concept: a publisher sends changes
-- to one or more subscriber databases automatically
EXEC sp_addpublication @publication = 'SalesPublication';
Real-world example A retail chain uses replication to automatically copy sales data from each store's local database to a central reporting database, giving head office near real time visibility into sales across every location.

Common follow-ups: What are the different types of replication available in SQL Server?;Does replication require a constant network connection between servers?

Always On Availability Groups;Backup & Recovery
All 7 Replication questions