This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 26%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
Greetings.
This coming weekend I'm upgrading a SQL 2016 instance to 2019 w CU 8 and the latest security patch. This guy does transactional replication to a 2019 instance w CU 7.
So my question is -- if I wanted to upgrade my replication instance ahead of time to CU 8 and the latest security patch, could I do it without first shutting down replication?
This doc says I first need to stop user activity on published tables, which isnt possible. However, thats in reference to upgrading the actual version.
Would replication survive the trip intact?
Thanks!
Additional SQL Server features and topics not covered by specific categories
Answer accepted by question author
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 78%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECZ%3C/text%3E%3C/svg%3E)
Hi,
It is not necessary to stop the replication when upgrading or patching the SQL Server at the Subscriber .
you may need to stop user activity on published tables when upgrading or patching the SQL Server at Publisher.
Upgrading or patching SQL Server instances requires a certain amount of downtime.
Complete as expected, thanks
I'll confirm here in a few hours, but am assuming this is accurate.