After a SQL Server cluster failover, SharePoint users could not open any page, though all SQL resources were online. Here is what we found and how we fixed it.
Windows Clusters in Different Domains: Deploying a Distributed Availability Group
After a merger, a client had Windows clusters in different domains that were connected but not trusted, and no wish to use certificates. Here are the steps I shared to deploy a Distributed Availability Group with NTLM pass-through authentication.
Migrate SQL Server Cluster Storage to New Disks
To migrate cluster storage for a SQL Server failover cluster, add the new disks to the SQL Server role, take the instance offline, copy the files with their permissions, give the new disks the old drive letters and bring the instance back. This post lists every step, the checks to run first, the quorum and MSDTC disks, and the T-SQL alternative that changes file paths.
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 – AlwaysOn Automatic Seeding – Database Stuck in Restoring State
A client used AlwaysOn automatic seeding for a huge database, but it stayed in Restoring state on the secondary. Here is the reason we found.
SQL SERVER- Unable to Failover AlwaysOn Availability Group to Disaster Recovery Site
A client added a DR node but was unable to failover AlwaysOn Availability Group to it. The listener had only one IP address, and here is the fix.
Restart Azure SQL Database: What Works and What Doesn’t
You can’t restart Azure SQL Database the way you restart SQL Server, because Microsoft runs the service. This post shows what to do instead: find and end the blocking session, scale the database, or trigger a failover. It tests the blocking query on a demo database and explains why a stack dump is not a restart.