Adding a database to an availability group can fail with the message that the database is encrypted by database master key, even when TDE is off. This post finds the key, checks what depends on it and lists three ways to continue. A demo database shows the checks and the error that protects a key still in use.
SQL SERVER – Always On Listener Creation Failure – Enabling Object ProdListener Failed With Error 5
I have written a few blogs where I explained a few issues about the failure of listener creation failure in a cluster. Let us learn about it.
SQL SERVER – Always On Listener Failure – Provisioning Computer Object Failed With Error 5
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
Error 35296: log backup on a secondary replica failed because the new backup information could not be committed on primary. Here is the cause I found.
Logical Name Mismatch: master_files vs database_files
A logical name mismatch means sys.master_files and sys.database_files disagree about a file name. A tested demo shows both views on one server, and a script checks every database. The post explains the secondary replica case and its fix.
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.
Availability Group Restore Error When You Add a Database
The availability group restore error appears when automatic seeding and a manual restore both fill the same secondary. The post explains the cause, shows read-only checks for the seeding mode and the replica roles, and gives the fix with its undo.