The scariest word for any DBA is – Database Downtime. Every DBA who is going off duty for the day or going away on vacation for a month is always worried about Database Downtime. I totally sympathize with everyone who is constantly worried about their database’s downtime. In the real world, we all know when our database does down, it means that our business is stopped. There is no other analogy we can give.
SQL SERVER – AlwaysOn Automatic Seeding – Database Stuck in Restoring State
As a part of my consulting, I observed that there is a lot of interest in using AlwaysOn availability group. I have deployed many AlwaysOn solutions from start-to-finish. Recently I encountered an issue and in this blog, we would discuss reason of an availability database to stay in restoring mode even after using automatic seeding.
SQL SERVER- Unable to Failover AlwaysOn Availability Group to Disaster Recovery Site
One of my clients took my assistance to deploy Always On availability group. After few months, they added a Disaster Recovery node to windows cluster and availability group also. Later, they contacted me that they are not able to move availability group to DR node. They were getting an error like below in event viewer.
SQL SERVER – Always On Availability Group Failover Generating Dump. Error: 17066: SQL Server Assertion: HadrFstrVnnUtils.cpp:479
One of my clients was using Always On availability group. They were having 3 nodes Always On AG setup. For simplicity, let’s call them Node1, Node2 and Node3. The first two nodes were in one subnet and node3 was in separate subnet. Let us learn about availability group failover.
SQL SERVER – Always On Availability Group Error 35250: The Connection to the Primary Replica is Not Active
Along with my performance consulting, I have also assisted many clients in fixing some quick issues. You can refer for various consulting services which I provide. During my consulting with various clients about Always On deployment, one of the commonly reported errors as below. (I have changed the AG Name, Node names to be more generic). Below came when we used the wizard to create an availability group. Let us learn how to fix error related to primary replica.
SQL SERVER – AlwaysOn Availability Group Backup fn_hadr_backup_is_preferred_replica Not Working Correctly
One of my clients has configured AlwaysOn availability group and wanted to automate backup to secondary replica. They debugged and found that the function sys.fn_hadr_backup_is_preferred_replica returns 0 no matter what the backup preference is set to. Since function was returning zero, the maintenance plan was ignoring the server to take backup.
SQL SERVER – AlwaysOn Wizard Error – Checking for Compatibility of the Database File Locations on the Server Instance that Hosts Secondary Replica
This blog is about another message which I faced with I faced in the wizard. You can read earlier two blogs with more problems which my client faced. This error is about AlwaysOn Wizard Error.