I am helping my clients with a Comprehensive Database Performance Health Check. Today we will see a very simple script to break mirroring in SQL Server.
SQL SERVER – AlwaysOn and Propagation of Compatibility Level
It is not possible to Propagation of Compatibility Level in AlwaysOn or mirroring from primary to secondary mirroring. Let us learn it today.
SQL SERVER – Database Mirroring Login Attempt Failed With Error: ‘Connection Handshake Failed. An OS Call Failed: (80090350)
Connection handshake failed with 0x80090350 on an availability group replica. What the code means, why it says mirroring, and what to check.
SQL SERVER – Error 9002: The Transaction Log for Database ‘SQLDB’ is Full Due to ‘DATABASE_MIRRORING’
Error 9002 has many causes. Here I explain the one where the transaction log for database ‘SQLDB’ is full due to ‘DATABASE_MIRRORING’ and what it tells you.
SQL SERVER – Unable to Start SQL After Patching – Database SSISDB is Enabled for Database Mirroring
After patching, SQL Server would not start. The SSIS hotfix script failed because database SSISDB is enabled for Database Mirroring. Here is the fix.
SQL SERVER – Mirroring Error 1456 – The ALTER DATABASE Command Could not be Sent to the Remote Server Instance
Adding a new witness server after a disaster failed with database mirroring error 1456. Here is one possible cause and what to check.
SQL SERVER – Always On Availability Group Error 35250: The Connection to the Primary Replica is Not Active
Joining a database to an availability group can fail with Availability Group Error 35250. Here is why it shows up in the wizard and how I fix it.