Close this search box.

How to apply patch on the Replication Topology for MS SQL Server

PatchingTwo week ago, in my previous post I have explained Steps to patch Always On Availability group of Primary and Two Replica. This week, in this post I will pen down steps on How to apply patch on the Replication Topology for MS SQL Server.

How to apply patch on the Replication Topology for MS SQL Server

Step 1: Patch the Distribution server

Step 2: Patch the Publisher server

Step 3: Patch the Subscriber server

There are also questions that if we need to pause or cancel the replication jobs? As far as I know, we don’t need to as it will be taken care. When we patch distribution sever the transactions will be there on Publisher’s log until the Distribution server comes back and is started again. While we apply patch on the Subscriber server the transactions will be there on Distributor server.

We all know this and do backup databases before applying patch, but, there is a tip, while backing up and restoring databases participating in Replication we need to preserve replication settings, read more about that in the  article.

In the upcoming post I will pen down steps to apply patch on the Mirroring servers.

Leave a Reply

Your email address will not be published. Required fields are marked *

Picture of Hemantgiri Goswami

Hemantgiri Goswami

Throughout my extensive 24-year tenure in the IT industry, I have honed my expertise in SQL Server and cloud technologies. My qualifications include certifications in ITIL, Azure, and Google Cloud, and my professional journey boasts a consistent record of delivering top-notch, dependable, and efficient solutions across diverse clients and domains. In recognition of my dedication and impact, I am honored to have received the Microsoft MVP award for SQL Server on six occasions. Additionally, I actively contribute to various online forums and blogs, acting as a moderator and facilitator of meaningful discussions. My ultimate mission revolves around empowering organizations to enhance the reliability and efficiency of their SQL Server implementations while fostering a culture of continuous learning and growth within the SQL Server community.