August 26, 2018 at 10:03 pm
All,
I am trying to find an answer to a question that has been plaguing me for the last couple of days related to AlwaysOn. Since the system Dbs cannot be configured for AlwaysOn, in the event of a Db corruption on the Primary Replica, the SQL instance would go offline and the AG fails over automatically to the next available replica and assumes Primary role. How do we ensure that the system databases are synchronized in the newly assumed node. As far as the logins, jobs etc we typically migrate the SQL logins and windows logins during the preliminary setup itself. But is there anything that we need to be proactive of? (Particularly when system database corruption is concerned?)
August 27, 2018 at 2:16 am
System DBs simply aren't synchronized in AlwaysOn - each participating node has it's own SQL Server instance with it's own system DBs and any changes made therein will affect only that server. If you're patching / upgrading the server or making any other changes to the system DBs that you need to be synchronized across nodes, then the short answer is that you need to apply every change to every node individually, so scripting things is generally a pretty good idea. 😉
Vegard Hagen
Norwegian DBA, occasional blogger and generally a nice guy who believes the world is big enough for all of us.
@vegard_hagen on Twitter
Blog: Vegards corner (No actual SQL stuff here - havent found my niche yet. Maybe some day...)
August 27, 2018 at 3:43 pm
Vegard,
Thanks for the input. I was thinking in similar lines too. Makes me confident now :).
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply