Share via

SQL - Always on avilabilty - Patch updates

KIRUBAKARAN J A 21 Reputation points
2020-12-03T12:43:52.393+00:00

we have servers SQL always-On config like below,

Node1 -- primary
Node2 -- seconday1 (automatic ,synch)
Node3 -- secoday2 (manual, synch)

we plan to update patch on both seconday1& 2 on weekdays ( like Wednesday), then Sunday on primary.

so the secondary node updated on Wednesday. till Sunday the Primary is not upto date.

is this create any noise? what are the cons on this ?

we have 1day downtime on sunday only , so that we plan all primary on sunday.

SQL Server | Other
SQL Server | Other

Additional SQL Server features and topics not covered by specific categories


2 answers

Sort by: Most helpful
  1. AmeliaGu-MSFT 14,016 Reputation points Microsoft External Staff
    2020-12-04T06:19:10.233+00:00

    Hi @KIRUBAKARAN J A ,

    what are the cons on this?

    In addition, during the upgrade process, a secondary replica will not be available for failover or for read-only operations, and after the upgrade, it may take some time for the secondary replica to catch up with the primary replica node depending upon the volume of activity on the primary replica node.
    For recommendation about upgrading Always On, please refer to this official documentation.
    And as Shashank said, it is better to apply patches on AG’s all nodes on Sunday.
    Best Regards,
    Amelia


    If the answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
    What can I do if my transaction log is full?--- Hot issues November
    How to convert Profiler trace into a SQL Server table -- Hot issues November

    Was this answer helpful?

    0 comments No comments

  2. Shashank Singh 6,251 Reputation points
    2020-12-03T13:39:03.353+00:00

    is this create any noise? what are the cons on this ?

    No it should not, as a matter of fact lot of AG users do this. And since you are updating primary on Sunday you should be good. Just make sure if failover happens between this period you "may" see some issues. So get approval from management on this. I answered similar question on how-long-can-cu-and-sp-be-different-across-a-sql-server-always-on-cluster-nodes

    we have 1day downtime on sunday only , so that we plan all primary on sunday.

    1 day downtime is enough to patch whole AG why are you then planning to keep nodes on different CU level ? I would suggest apply patches on all nodes on Sunday. You will be happy and so will be your customer.

    cons

    Please note that applying SP on secondary replica would need a reboot, most likely and you need to make sure that AG dashboard is in Sync before doing reboot. You need to be careful. If you want to avoid this risk do it on Sunday when you have a day downtime.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.