4

From documentation The Caveats section of the Availability group database level health detection failover option doc has some info that might improve our guesses on the question: It is important to note that the Database Level Heath Detection option currently does not cause SQL Server to monitor disk uptime and SQL Server does not directly monitor database ...


4

You can't depend on the system databases being cached in memory, more likely they won't be because of their less frequent access relative to the user databases. I think you'll end up in a quasi-functioning state, where your user databases will still be accessible but certain features of the server instance that rely on master and msdb will throw some weird ...


3

Since the log file is only growing on the secondary replica, something is preventing transaction log truncation on that database (but not on the primary). You'll need to check the value of log_reuse_wait_desc in sys.databases on the secondary replica to see why the transaction log isn't being cleared there. Since log_reuse_wait_desc is currently showing &...


3

Depends on what kind of offline. I had it get itself into a state where it had no idea what transactions were committed because the failure mode it was seeing was writes to the dbs were failing at block levels. It spammed the log nicely, but couldn't recover until I manually bounced it as it would believe the in-memory copy was correct after hitting the IO ...


2

It turns out, the process was working normally, but I was missing a step at the end. Once I had configured the availability group, I didn't know that I then had to connect to the remote server and add the database. In the tutorials I had found online, none had included that step. It was a small but significant item. Once I added the database on the remote ...


2

I can not see your script but I am assuming you get orphaned users on the database after the failover because the users are linked to SQL Server local logins with different SIDs on the different instances. The best way would be to recreate the login with the same SID in both instances CREATE USER SID=<sid> so you do not have to fix orphaned users every ...


1

The cluster core resource can be primary in one of the nodes without affecting the singles AGs and their assignament to a specific node. It is different from a Failover cluster Instance where there is dependency from the cluster core resource and the clustered service. I suggest you to manage AG failover inside ssms moving then with the proper wizard or by ...


1

the failover cluster instance is not a active-active solution for databases. Here you can find the microsoft documentation: https://docs.microsoft.com/en-us/sql/sql-server/failover-clusters/windows/always-on-failover-cluster-instances-sql-server?view=sql-server-ver15 The secondary node(s) is(are) not accessible (their sql server services are stopped). You ...


1

try to give the VCO AD object full control on the listener AD object. To do this, go to AD user and computer, locate the listener object, open properties, security and verify if the virtual cluster object is here and if it has full control on this object. Then retry the failover.


1

Something you were trying to do in May 2020 is doable now. In SQL Server 2019 CU8 (released 01/10/2020) they have added support for Distributed Network Name. Have a look at this KB4578579 - Improvement: Availability Group listener without the load balancer in SQL Server 2019 Also for instructions on how to configure dnn take a look at this atricle Configure ...


1

In my case Netlogon service was is disabled mode on secondary server hence we received this error. Once we enabled the same database came into sync.


1

The documentation! doesn't seem to require the secondary be in ASYNCH mode, however. It only says set to "MANUAL" failover. Under the "NOTE" section. "Upgrading a synchronous-commit replica and taking it offline will not delay transactions on the primary. Once the secondary replica is disconnected, transactions are committed on the ...


Only top voted, non community-wiki answers of a minimum length are eligible