Transactional publication with queued updating subscriptions
The client I worked with had two data-processing centers located miles apart and linked by a reliable T2 network connection line between the sites.The client needed a flexible high availability solution that would allow the addition of a third site in the future with minimum effort.Once we find out the problematic agent the next step is to identify within the agent which particular thread causing the issue.Let me introduce you to the important threads and its work on these replication agents in nutshell.Each existing site hosted a SQL Server 2000 database on a Windows 2000 server.Both Windows servers had two processors and 2GB of RAM.Reader thread – It finds the watermark from the table Msreplication_subscriptions(on subscriber) and uses this information to retrieve pending commands from the Distribution database.It basically uses the stored procedure sp_MSget_replcommands to achieve it.
Replication can be thought of in terms of the newspaper model - the publisher produces the newspapers and sends them to the distributor, who separates and sends them on to the subscribers (e.g.
I'll give you some background about this case and show you the steps I used to create a solution that doesn't require extensive scripting skills.
If you're looking for an easy-to-use solution for your organization's high-availability and disaster-recovery needs, taking a look at this real-world example can help you decide whether merge replication is a good choice for you.
As soon as the initial snapshot is taken, subsequent data changes and schema modifications made at the Publisher are usually delivered to the Subscriber as they occur (in near real time).
The data changes are applied to the Subscriber in the same order and within the same transaction boundaries as they occurred at the Publisher; therefore, within a publication, transactional consistency is guaranteed.