I have written a few blogs on issues about the failure of listener creation in the cluster. In this blog, we will explore listener creation failure.
SQL SERVER – Error 35296: Log Backup for Database “SQLAuthority” on Secondary Replica Failed Because the New Backup Information Could Not be Committed on Primary Database
Log backup for database “SQLAuthority” on secondary replica failed because the new backup information could not be committed on the primary database.
SQL SERVER – Automatic Seeding of Availability Database ‘SQLAGDB’ in Availability Group ‘AG’ Failed With a Transient Error. The Operation Will be Retried
Earlier I have written few blogs about automatic seeding feature. In this blog we would learn how to fix error: Automatic seeding of availability database.
SQL SERVER – Add Database to Availability Group Failure – This BACKUP or RESTORE Command is Not Supported on a Database Mirror or Secondary Replica
In this blog post, we will fix the error related to This BACKUP or RESTORE command is not supported on a database mirror or secondary replica.
SQL SERVER – Different Size of COPY_ONLY Full Backup on Primary and Secondary Replica in Always On
We will learn how the full backup size can be different on the primary and secondary replica for an availability database in Always On availability group.
SQL SERVER – Automatic Seeding of Availability Database ‘DB’ in Availability Group ‘AG’ Failed With an Unrecoverable Error
While deploying Always On Availability Group with a client, they found that when they use automatic seeding, the database was not shown on secondary. After digging more, we found that it was there earlier in “Restoring” state when seeding was in progress but then it automatically disappeared from the list of databases on secondary. Here is the option in the wizard.
SQL SERVER – T-SQL Script to List Automatic Seeding of Always On Availability Group
I love blog post which just solves a simple point and immediately gets us the necessary answer. Recently during one of the consulting engagement Comprehensive Database Performance Health Check at one of my customer place we identified a wait statistics which was related to SQL Server Always On Availability Group. The wait statistics issue was VDI_CLIENT_OTHER and the way to solve is blogged here SQL SERVER – Many BACKGROUND Threads with Command VDI_CLIENT_WORKER. We needed to remove automatic seeding to reduce the said wait statistics.