sql server fail over cluster changes on sql server

Sql server 2012 running on
node1, node2 running on fail over cluster manager windows 2012 and shares the same disk, node1 is active..


1. How do i plan to install new patches(kb,Sservice packs,etc) of SQL for the both nodes?
as some sql patches requires restart? I need to patch on both nodes?

2. If change any database settings in node2 or node1, will it replicate each other?

3. what precautions and planning i need to, during changes on the Sql servers. Pls suggest

4. what about if any windows updates or any windows patches needs to restart?
bsarahimAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Sajid Shaik MSr. System AdminCommented:
here the microsoft documentation about the cluster rollup and service pack installation

https://support.microsoft.com/en-us/help/958734/sql-server-failover-cluster-rolling-patch-and-service-pack-process

all the best
0
Vitor MontalvãoMSSQL Senior EngineerCommented:
1) You don't need to patch both nodes but it's highly recommended to do so as databases behaviour might be different if missing a hotfix. You should apply the hotfixes in the Passive node first and restart that node. Then you should schedule a day and time to failover the Active node to the Passive node (usually during night or weekend) so you can install the hotfixes in the now Passive node as the SQL Server instance will be running on the now Active node. You can schedule again a Failback if necessary.

2) There's no replication in a cluster environment. Changes made on a database will be immediately effective no matter in which node the database is running.

3) Check my answer 1).

4) Check my answer 1). Always apply on Passive node first, schedule the failover, apply on the new Passive node, schedule failback if necessary.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SQL

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.